QUOTE(neuroshock @ Oct 24 2005, 10:21 AM)
A few quick questions.
In the new release 1.0 rc3 (or rc4 that's supposed to be coming out tonight)
Is the now famous "Fast Kernel" already a part of the rom, or does it come with the stock kernel?
Also I see that the various keyboard issues seem to be fixed BUT, can a mouse be used with the Guyhelm rom like the stock kernel/Sharp rom can with cwaig's fixes? or are those already incorporated into the rom? If not what would I need to do to get usb mouse functionality with the Guyhelm Rom?
Um while I'm thinking about it, how does the Guyhelm rom handle IR keyboards? My ThinkOutside Stowaway worked on the the standard sharp kernel with the irk package installed. Is the same fix valid here, or is that already integrated into Guyhelm Rom as well?
And last but not least, are there different memory configuration variants with Guyhelm? For example we use the os installed on an sdcard in the same way we used to do with the old cacko rom's and the sl-5500's and achieve a 64-0 memory config to maximize the mem availability for running programs on Guyhelm/sl-6600l?
Thanks a bunch,
1. The fast kernel is included by default in the ROM. I try to do consistent work - include all my stuff in one easy to install thing :-) Next candidate is the fast libSDL, for which someone requested me to add a good mame support (1).
Please see externe.net/zaurus/kernel for a README explaining how to use the fast kernel on a default ROM. I do not support that - I just provide instructions. It should be enough to fix the USB/bluetooth keyboard problems, if you remove any keyboard fix you have installed.
2. A mouse can be used *by default* - whether it is usb or bluetooth. I do use a bluetooth mouse + keyboard daily. I recommand you the Stowaway because that's what I use and therefore support. Everything else may (99%) or may not (1% odds) work.
3. I dropped IR keyboard support long ago, because it was not satisfied hardware wise and software wise. The hardware requires a line of sight. The software is not standard, and can not work in console mode. I could try to fix IRK, but it will require a IR keyboard and hacking IRK. I do not have an IR keyboard to test that.
4. Memory configuration - on the 6000 you have 64 Mb of RAM and 64 Mb of flash, half of which is writtable by default (/home) while the other half is not (/)
I changed sharp settings to have 64 mb writtable (/). There is no need to put the root filesystem on a SD, unless you have a huge root filesystem. I was asked to support (2) a huge root filesystem, which I tested and used daily, but no longer use since I couldn't get my hands on a microdrive- the default qtopia scripts wait for the SD to be mounted before starting it.
Simply put /opt on a SD, or maybe also /home with it too, and create symlinks to it. It is quite easy : format your SD in ext2, cp -adr the files, rm -fr the originals, ln -sf from the SD to the Zaurus, and voila. On next reboot, qtopia will wait for the SD to be mounted before starting. You can also specify a fsck after reboot.
(1) and (2) helped me acquire hardware I wanted to support, therefore their request went on high priority. At the moment, I'm thinking about getting a spare 6000 to work on the distribution, because I use my 6000 daily - it's a work tool. I was offered a dead 6000 to practice on the flash and ram upgrade, which will certainly speed up everything because I wouldn't take that risk on the 6000 I need everyday. That also means I do a release only when I'm quite sure I won't do one for long time, since I must remove all my settings/put back defaults, etc. This is also why the wlan and ipkg bugs were introduced :-/
A dedicated 6000 will certainly help development. Donations to email@example.com or even a working 6000 are welcome !