QuantumSTEP currently runs on
a) Sharp Zaurus with Sharp ROM and Linux 2.4.xx kernel
b) Acer n30 with Letux Linux (but quite old - end of 2006)
c) OpenMoko Neo 1973 with quite old OABI kernel (August 2007)

The reason and the good side with this is that there is a single image
that runs on all these platforms (OABI hardfloat ARM code).

The downside is that newer developments and bug fixes are not
included. Especially for the OpenMoko but also the Acer n30 could need
some improvements (the kernel has no ext3 support, no PPP support - so
there is no Internet Access over Bluetooth).

So, I have started to install and learn how to compile new kernels
with mokomakefile/openembedded. The result after some days of building
5000 packages is promising - but does not work. What I have got so
far:

Acer n30:
* a new kernel based on the OpenMoko system that works halfway with
the old rootfs but has some issues with the power key
* a new rootfs from OpenMoko system boots and launches the touch
screen calibration - but then hangs (maybe the touch driver is
configured for a Neo and not the Acer)
* the device does not respond to ping although the USB CDC Ethernet is
up (maybe a config error)

Neo 1973:
* the new kernel boots but hangs in a strange state where it just
prints on the console that the power or the AUX key is pressed
* X11 does no boot

Does anyone of the readers on this list have hints or wants to help
testing/patching/debugging?

Nikolaus

The main trick was to link the memory card into the file system and
modify qssh since the Linux is quite spartanic (e.g. no fgrep, no
ldconfig) and the initial $PATH contains only one location where it is
possible to add executables.  So, installation is a little tricky.

But I could start e.g. the open or defaults commands and they did
print some messages coming from NSLog until they failed because there
is something bad with finding the mainBundle.

The device has no X11 server (yet). Maybe it is possible to get X/Qt
working which would allow coexistence with the existing Qt system.

So, it is the fourth (ARM based, handheld) device where something
runs. The next step will be to set DISPLAY to a display.

Questions welcome.

-- hns