Guylhem Rom: First Qtopia 1.5 Release

[adf]

it's simple, really. just su
and do mkdir /mnt/card/tmp  (or mnt/cf/tmp if you prefer it on cf) and then do
ln -sf  /mnt/card/tmp /tmp

do it from a console in qtopia?  This is exactly how I fixed the install issue.

you could remove /tmp first.
or do ln -s instead of ln -sf (though i expect you'll get an error)

[rip]

i appologize for my incompetence, but witch /tmp have i to remove?

and also is there any fix for the add/remove applet only showing internal memory as the only path for install?
am i the only one to have this pb?

[gfdsa]

add/remove applet  ?
how to get there? i have all the panel filled with stuff i want to remove

[rip]

well, sorry, windows typology rests....

icon name under settings is "software"
when installing anything cliked, only one choice offered: internal.

also gulhem, i have an air cable, do you know how to configure that?

[adf]

if you are in a console in qtopia there is, effectively, only one /tmp...the one inside QtPalmtop.rom

as to the applet thing....if they don't come up in add/remove, you could try subapplet? a I don't know it that handles uninstalling, though.

the gui packagemanager internal only option is a kind of side effect of this setup, imho.  because QtPalmtop.rom can be anywhere (any one try it over nfs yet?--might be an interesting soution to situational work/home/school demands) it is difficult to say it should definitely look outside itself.  I suspect, though that you could edit ipkg.conf and do install -d from commandline.
 Personally I prefer having all of th z-rom stuff onboard. it lets me mix and match cf and sd stuff freely without concern that i'm scrambling my sytem. (the tmp and var thing should probably be scripted, though) zright now, if I want something more than qtopia ioffers I use pocketworkstation on my sd--all self contained as well. (hmmmm the possibilites for cheap arm based desktops with mobile self contained os that can be transferred to other devices or used as thin clients.....)

[adf]

IRK.

the "a" key on my ir keyboard does not work. the other keys all do. the "a" key sends ? to irk--which i take to mean that it sends something, but irk has no idea what. I suspect this is a by-product of the keymap fix.  Any ideas for a fix for this? maybe a boot time thing that connects the ir kbd pre qpe?  out of my depth here, obviously

USB

hid, usbmouse and usb kbd don't seem to autoload...and loading them after booting into Qtopia is a pain. (didn't bother w/ the mouse)

since no one seems to own 6k N models, at the very least both usb (with kbd mouse and storage support --including the toshiba module--don't know if you did that or not, just thought it should be mentioned)
and wireless  should probably be compiled in. the extra kernel size isn't much and the result is good.


Qtopia 2.1
lpotter says 2.1 is sharp package compatible.. ( I was just pestering him about this... see the qtopia 2.1 available soon thread) and has a sane dir structure to boot. It warrants more investigation, maybe?
Maybe 2 rom versions? a qt2.1 "sharp" and a qt 2.1 "floating point" down the road?

Idle speculation
any possibility of a pdaX version?

[adf]

IRK.

the "a" key on my ir keyboard does not work. the other keys all do. the "a" key sends ? to irk--which i take to mean that it sends something, but irk has no idea what. I suspect this is a by-product of the keymap fix.  Any ideas for a fix for this? maybe a boot time thing that connects the ir kbd pre qpe?  out of my depth here, obviously

USB

hid, usbmouse and usb kbd don't seem to autoload...and loading them after booting into Qtopia is a pain. (didn't bother w/ the mouse)

since no one seems to own 6k N models, at the very least both usb (with kbd mouse and storage support --including the toshiba module--don't know if you did that or not, just thought it should be mentioned)
and wireless  should probably be compiled in. the extra kernel size isn't much and the result is good.
though i seem to rmember problems compiling hid in the last kernel -- I skipped it and just did the lesser mouse and kbd options...

Qtopia 2.1
lpotter says 2.1 is sharp package compatible.. ( I was just pestering him about this... see the qtopia 2.1 available soon thread) and has a sane dir structure to boot. It warrants more investigation, maybe?
Maybe 2 rom versions? a qt2.1 "sharp" and a qt 2.1 "floating point" down the road?

Idle speculation
any possibility of a pdaX version?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79329\"][{POST_SNAPBACK}][/a][/div]

[guylhem]

installating in other places besides internal flash: I'm working on that. I have no idea why the file manager tab doesn't show my SD card, but shows my CF card. The installation target could be set by editing /etc/ipkg.conf

too many apps by default: sorry, but I think they should all be included. most roms are just roo empty. remove if you want, but let other people who won't get apps by themselves take advantage of the already selected apps.

irk: you're right this is a byproduct. edit your driver to send keycode 125 for A, and 30 for the key you want to act like FN. Sorry, there is no other way. Sharp Qtopia 1.5 hardcoded that FN=30, even if for the rest of the keyboards in the world keycode 30 =A

usb : found the bug. Forgot to include stuff in my kernel compilation. Fixed.

I'll try to release an update soon.

[ken]

>installating in other places besides internal flash: I'm working on that. I have no >idea why the file manager tab doesn't show my SD card, but shows my CF card. >The installation target could be set by editing /etc/ipkg.conf

Tried that a while back, doesn't work.

>too many apps by default: sorry, but I think they should all be included. most >roms are just roo empty. remove if you want, but let other people who won't get >apps by themselves take advantage of the already selected apps.

There's just a few that I'm thinking you might want to exclude, mainly because they're actively updated.  Otherwise not a biggie.

[adf]

I had wondered about the usb thing after I posted that. It looked like at least some of the stuff was laready compiled in as it loaded.

will do with the key thing... should be no big thing.

will try to get oe going in the next day or two,

[adf]

doing a fastffpe kernel with the usb fix btw?

and on oe.... do you want me to test it before tarring it? It will make the thing a good bit   bigger, but will likely save time, and you'll get a cmplimentary copy of nano  

[guylhem]

Hello

ken : if ipkg.conf doesn't help, I'll have to see where the problem is.
Regarding apps, which one should be updated? Updating them at each release is not a problem.

adf: just compile "USB support for HID devices" in Drivers/USB section. I compiled only a part, and that didn't really help.
For oe, I'm only interested in the toolchain. Just follow the instructions (I can't - I hate following instuctions. I have to try by myself) from oe website and you'll end up with many .ipk and a cross compiler.

I'm only interested in the cross compiler. Locate where it is (it features files such as arm-linux-gcc) and to a .tar.gz of the uplevel directory. Try to run arm-linux-gcc -v to see which version it reports. Then send me a list of the files in that tar (tar ztvf file.tar.gz > list) so I can quickly check is everything is there.

Guylhem

[rip]

this quick post to ask if its not a good idea to include zeditor and a pdf reader in rom apps coming with flash restore. i hate vi and i don't know other console editor.

[adf]

Hello

ken : if ipkg.conf doesn't help, I'll have to see where the problem is.
Regarding apps, which one should be updated? Updating them at each release is not a problem.

adf: just compile "USB support for HID devices" in Drivers/USB section. I compiled only a part, and that didn't really help.
For oe, I'm only interested in the toolchain. Just follow the instructions (I can't - I hate following instuctions. I have to try by myself) from oe website and you'll end up with many .ipk and a cross compiler.

I'm only interested in the cross compiler. Locate where it is (it features files such as arm-linux-gcc) and to a .tar.gz of the uplevel directory. Try to run arm-linux-gcc -v to see which version it reports. Then send me a list of the files in that tar (tar ztvf file.tar.gz > list) so I can quickly check is everything is there.

Guylhem
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79436\"][{POST_SNAPBACK}][/a][/div]

Will do.
You want the 2.95 kernel cross compiler stuff too?  there isn't really much to that.. just a matter of taking the standard 2.95 xcompiler and changing a couple names -like arm-linux-gcc to arm-linux-gcc2.95, or something very close. it is just a naming thing to make bitbake.conf happy. It is the same cross compiler you are already using, i bet. I used the same cross compiler to do oz and the integrated version of your kernel last month... took about 10 characters to switch it back and forth.

I take it you are planning to patch an oz kernel, compile opie, pull opie, repartition, install the new kernel and put opie in place of the current Qtpalmtop.rom?  

If so, want to give gpe a go?  if gpe were done this way, and the Qt stuff run on it the way it has recently been done on pdXrom (so that qt apps can be run) this woud be real interesting--esecially if it were tweaked to run stuff from multiple feeds (like debian arm... ) The only real issue i saw with the last gpe was that the supplied minimo didn't quite work right--and of course the small feed.

this brings up something i've been wondering about... have you noticed that op and matchbox are both in debian? make the sd / and the nand /boot (?) and use the debconf and debtools and kdrive that oe builds and a native debian might be possible.

re the hid thing... i don't have a menuconfig in front of md, so I'll be a bit vague....
in usb under hid there are raw (?)? mouse and kbd support options.  on the previous kernel version I could compile those, and they'd drive a usb mouse and keyboard, but not the hid option.  Full hid never quite compiled... i always ended up hang ing on to the module, though it didn't get used, I don't think

[gfdsa]

speaking of multiple guis, one of the ideas that i did like in guylhem ideas was having guis on sd or cf, and leaving possibility of fbcon only device, then it could be brought to situation when you can manage the stuff similar to xdm, for example qingy, which is an DirectFB based login manager, which im trying to compile for arm now
for pdaXrom stuff - its simple, there should be only --prefix=/opt/pdaXrom added, and assuming you have a sym link or you mount your SD to /opt, it will run, may be with some light scriptiing for library pathes, for GPE, i should look how it's compiling system is implemented, but im pretty sure that its possible to have all gpe's stuff inside one directory
then it all can be packaged, or t least tarballed with some pre- and post- installation scripts, and distributed