now it seems the most actuals sources are at muromec's qtopia-ezx at master - GitHub .
Anyway take look at thoses pages:
qtopia4-ezx-build - Mobile Linux Development Community
qtopia4-ezx-faq - Mobile Linux Development Community
Get here: http://ezxdev.org/qtopia/experimenta...080925.tar.bz2
Unpack, move to /opt/toolchains:
add to PATH:Code:tar jxfpv arm-iwmmxt-linux-gnu-qtopia_all_20080925.tar.bz2 sudo mkdir -p /opt/toolchains/ sudo chown /opt/toolchains/ mv arm-iwmmxt-linux-gnu /opt/toolchains/
Use!Code:export PATH=/opt/toolchains/arm-iwmmxt-linux-gnu/qtopia/bin:/opt/toolchains/arm-iwmmxt-linux-gnu/bin:
"Hello world" app: http://ezxdev.org/qtopia/hello.tar.bz2
Unpack, go to dir and build:
Upload to phone and run:Code:tar jxf hello.tar.bz2 cd hello qtopiamake make
docs: http://doc.trolltech.com/qtopia4.3/ и http://doc.trolltech.com/4.3/Code:scp hello root@192.168.10.6:/root/ ssh root@192.168.10.6 /root/hello
Last edited by muromec; 10-26-2008 at 05:41 AM.
now it seems the most actuals sources are at muromec's qtopia-ezx at master - GitHub .
Anyway take look at thoses pages:
qtopia4-ezx-build - Mobile Linux Development Community
qtopia4-ezx-faq - Mobile Linux Development Community
Say developer, but it's so hard!
If you want to contribute, look at how to build on wiki links above and you should know :
There is possibility form the sbf_flashed_phone, to replace all files in the rootfs, (writable rootfs) so you can use the autobuild files with some chroot method, or overwrite the rootfs, in a crazy update, using a bootusb'ed kernel with some tools on a rootfs on sd, or a rootfs on nfs.... Well, you can do as if the flash was a hard disk in a desktop PC.
If you prefer, you can mkfs.jffs2 your new rootfs's folder and re flash it at 0x19E0000 (max 38Mb as the home folder and all stuff are already in the first addresses).
There is an Openmoko/FIC's qtopia, that will run on the phone (EABI, tested with an openezx kernel usb_booted), maybe it's documented ... (i don't know why, i've just avoided qt-extended website in the past...)
Last edited by sabrod; 03-06-2009 at 10:11 PM.
Say developer, but it's so hard!
>directory autobuilds contains files like image * jffs2.bz2 and * tar.bz2 rootfs/Angstrom*
image-$date.jffs2 is a qtopia fs image flashed to /dev/mtd9 ( mounted to /opt )
in image-$date.tar.bz2 the are same files packaged into tar archive
rootfs/Angstrom* is an angstrom rootfs image flashed to /dev/mtd8 ( mounted to / )
you also need a kernel with changed mtd map and removed write lock
( for E6 use http://ezxdev.org/qtopia/misc/kernel/kernel_e6_003 )
Last edited by sabrod; 03-03-2009 at 06:30 PM.
Thanks you Muromec
So one can simply reflash a modified ".sbf", with cg's edited and repacked by some ".smg" substitution using any modding method, i suppose i'll try and flash my a910 as i need to do 2.4 kernel stuff.![]()
Say developer, but it's so hard!
Code:93 },{ 94 name: "ROOT", 95 size: 0x01720000, 96 offset: 0x001A0000, //JFFS2 root size is 23MB 97 },{ 98 name: "OPT", 99 size: 0x02620000, 100 offset: 0x019E0000, //JFFS2 opt size is 38MB 101 },{
oh, this changed, (i think root of now was home sooner, and opt was root sooner too?)
btw, now genblob read if there is a kernel in flash (if it have a 32bit flag, and is at the right place,128k next to genblob start, if that fit...and that generally does) before trying to read mmc...as i know you worked and searched in this direction, i tell you, if you want to change your patchses, etc...
Also, do you have a ezx.c (2.6) patch for the right framebuffer's colors?
Say developer, but it's so hard!