QUOTE(futaris @ May 15 2008, 05:51 AM)
QUOTE(speculatrix @ May 5 2008, 07:41 AM)
Technically, there's been quite a lot of discussion about it, enough for people to retrace all the steps anyway. The cleverest bit of work was done by someone else* to wrote a wrapper which changed the framebuffer mode to QVGA and ensured the right pseudo sys and proc files existed (in a chrooted environment).
I am genuinely sorry that the excellent work (all I did was start the idea and then help someone else do the clever stuff) hasn't been made available.
Don't suppose there's been a single post detailing these what pseudo /sys and /proc files are needed in the chroot environment, and how to extract the files?
I believe so, but briefly:
* use opentom projects ttimgextract to split the "system" file into the kernel/initrd and the file system (cpio)
* create chrooted environment, e.g. /home/tomtom, unpack the cpio files, copy in /dev (can't mount/bind as you need to take devices using files), create proc and sys.
* mount/bind the SD card, or copy over the files if you've got a C3x00 and so have sufficient room in /home/tomtom
* copy in additional binaries from main angstrom/debian distro so you can chroot
* start the ttn binary with strace, record its output and observe what it's trying to open. fix problems.
the pseudo proc files can be determined using tables on opentom website.
I will see what I *can* release without getting scared