Bringing Cacko 1.22 To Sl-c3k/sl-c1k

[iamasmith]

Hi all, and particularly Anton,

Well I got my SL-C3000 and it ain't as scary as it looked with no information. I have learned a reasonable amount about the hardware and am doing some preliminary testing to see if I can get as much of the Qtopia environment from Cacko 1.22 as possible running on the 3K.

This I view as the first step, then sort out scripting etc. for the environment and then use try with a 'Special Kernel' for the 3K.

What I have done so far.

1. Reinstalled Cacko 1.22 lite on my 860 (soon to go), and from the most basic install have tarred off everything excluding /mnt,/tmp,/proc and /dev to a tar file - the intention is initially to flatten the install out and worry about reassembling it into RO sections later etc.

2. Created a 256Mb file containing an ext2 file system and restored the tar there.

3. Created mount points in the ext2 file for /dev,/tmp,/mnt,/proc

Now the interesting bit.

4. Boot up the SL-C3000 using key combination D+B (instead of D+M) and this boots into the flash only Linux distro.

5. Insert the SD card containing the file 256Mb ext2 file and...

mount /mnt/card/cackolite-ext2 /mnt/cf -o loop
mount -o bind /dev /mnt/cf/dev
mount -o bind /proc /mnt/cf/proc
mount -o bind /lib/modules /mnt/cf/home/root/modules
chroot /mnt/cf /bin/bash

This mounts the ext2 file system over the mount point for the CF (so I don't need to create another one) and uses the bind facilities of the kernel to mount the existing /proc,/dev and modules directories into the ext2 file system.

Finally the chroot repoints the root to the file system in the 256Mb file and launches bash. This all works admirably and I can run all the command line stuff.

I had already replaced /usr/QtPalmtop.rom/lib/libsl, libt and libqpe with the 3K versions and had replaced qpe/runqpe and qeserver in the /usr/QtPalmtop.rom/bin directory.

6. Run /sbin/launch

At present I get the Cacko welcome screen, then the build drops back to a terminal prompt but is completely frozen.

So, anyone know what holds the other hardware dependencies for the SL-Cxxx models?

I think I need to get rid of anything in the following categories..

* ATI W100
* Hi Res Battery monitoring (initially because no special Kernel to expose the counters)
* /proc/cccr_change stuff - obviosuly the current ROM is set with values specific to the SL-Cxxx range. This shouldn't be dangerous at the moment because the standard Kernel does not expose this stuff but DOES need removing before switching to something like the Special Kernel.

Final point that's interesting... Move the modified ext2 file back to the 860 and you CAN boot with the newer versions of libsl etc..., unfortunately it runs portrait only. But at least it proves the chroot environment does boot.

So, any pointers that will cut down on the number of reboot cycles that I need?

- Andy

[Stubear]

You might want to try grabbing the latest rom update for the C3k from Sharp (http://support.ezaurus.com/sl-c3000/update/c3000update/kyodaku.asp) and mounting the initrd.bin on your desktop to see what the layout of the ROM is.

Also you will need to look at how hdimage1.tgz is laid out filesystem wise and decode the updater.sh script to see what magic it does with the hdimage1.tgz during flashing.

Only having a C760 at present, I've only looked at hdimage1.tgz for files I could use on the C760 (and even then before I got most of them working Cacko relaesed them in their feed )

The rc scripts would also probably give you a heap of information - from memory they are responsible for mounting/restoring the readonly filesystems on the Cxx0 zaurus

Stu

[maslovsky]

Here are the problems you'll run upon when trying to run Cacko on C3000:

 - kernel image (obviousely)
 - kernel modules
 - ROM layout
 - Qtopia binaries
 - wireless drivers
 - bluetooth drivers

[iamasmith]

Here are the problems you'll run upon when trying to run Cacko on C3000:

 - kernel image (obviousely)
 - kernel modules
 - ROM layout
 - Qtopia binaries
 - wireless drivers
 - bluetooth drivers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=70964\"][{POST_SNAPBACK}][/a][/div]

OK, thought I had explained what I was doing at this stage.

Not running the kernel or modules.
ROM layout.. no problem, flattened onto ext2 filesystem stored in a file, mounted -o loop with bind mounts of the real /proc /dev etc. into the ext2 file system.
wireless drivers.. later
bluetooth drivers.. later

Just trying to identify the Qtopia libs which are specific to the SL-Cxxx/ATI W100/Battery Granularity etc... so I can get the cosmetic bit going first.

BTW: Not trying to steal the baby here... just accelerate the program a bit.. will fully document everything that I come up with so that it can go back into the Cacko pool.

+ I have a couple of 'interesting' ideas on how we might be able to produce a unified ROM image that runs on the SL-C1000 AND the SL-C3000 by making the image part of a file system stored in a file and then either storing it in flash or on hdd

- Andy

[maslovsky]

All Qtopia libs must be taken from C3000 - the C8x0 version will not work on C3000.  

Thу battery granuality is in the kernel...

[iamasmith]

All Qtopia libs must be taken from C3000 - the C8x0 version will not work on C3000. 

Thу battery granuality is in the kernel...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=70999\"][{POST_SNAPBACK}][/a][/div]

Thanks Anton, I thought that the core ATI dependencies would be in specific libraries..

Guess I need to start pruning out specific stuff then. I have a Qtopia build environment so I will start with all the libs and ELFs that it generates..

Will keep you posted on how I get on.

[ev1l]

Now that we're on the subject of ROM re-building, what woud it take to run the standard Qtopia PDA edition on top of the Sharp (or self-built) kernel?

[iamasmith]

Now that we're on the subject of ROM re-building, what woud it take to run the standard Qtopia PDA edition on top of the Sharp (or self-built) kernel?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=71013\"][{POST_SNAPBACK}][/a][/div]

I'm not anticipating doing that for this exercise. Some of the Sharp Qtopia stuff may be hardware optimised and the details of how it is optimised are probably not going to become available any time soon.

I'm thinking particularly of the Zoom features on the VGA models that allow 320x240 running etc. I want to keep my initial efforts as compatible as possible.

- Andy