OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: louigi600 on May 03, 2008, 06:34:10 am
-
I just installed TTconsole on my tomtom ONE XL ... it's linux inside.
I wonder if it's worth while having a section in the "Model Specific Forums" ?
-
I just installed TTconsole on my tomtom ONE XL ... it's linux inside.
I wonder if it's worth while having a section in the "Model Specific Forums" ?
the opentom website and mailing list covers these devices nicely. what's more interesting is extracting the software from the device and running it on the zaurus
-
what's more interesting is extracting the software from the device and running it on the zaurus
Hey, wasn't someone working on that ages ago? Too bad he never got around to releasing anything...
-
what's more interesting is extracting the software from the device and running it on the zaurus
Hey, wasn't someone working on that ages ago? Too bad he never got around to releasing anything...
I think it did get working ... but required licences to run so in other words you neaded a tomtom hardware to have the licences.
Anyway unless Z gets working in an acceptable way on all models (I men I'm only satiftied with my c860 wile my C1K is a disaster) what's the point in running tomtom in Z if it crashes while you navigate !
I got the console on my tomtom and it works fine ... now mplayer is next ... and last but not lest some gaming !!!!
Anyway I recently got an AUSU EeePC that's 2.5 times the size ov a Z over all (around 1.5 times length and with ... while the height is not that different).
it has intel celeron CPU @900 Mhz 800x600x16bit display, working sd slot, 3 standard usb 2 slots, 4Gb solid state microdrive, 512Mb ram, integrated wifi (antherons), integrated 100Mb lan, integrated audio, integretad webcm and integrated VGA plug .... it only costs 299 Euro and runs some xabdros linux distro (and comes with drivers for installing win XP if you like).
Ok you will not run it for 8 hours or so .... but for 4 hours I think it's possible.
I'm currently postint with it right now.
-
what's more interesting is extracting the software from the device and running it on the zaurus
Hey, wasn't someone working on that ages ago? Too bad he never got around to releasing anything...
basically, I am too scared of being sued into oblivion by Tom Tom for making piracy feasible. Attempts to contact TomTom to ask them to allow me to release the toolkit did not give a response - I made it clear that it would not have contained any IPR of theirs. I also tried to contact a developer I'd encountered sort of via OpenTom, but he didn't respond, although he did ask one guy* who worked on it to go there for a job interview!!! I also asked TomTom if they could sell the GO software separately allowing zaurus owners a way of owning the s/w and maps legitimately, but failed to get a response.
I even hoped that someone from TomTom might turn up on these forums and take notice, but no. I suspect if they are aware, they'd be standing on the side-lines to see what happens!
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.
-
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?
-
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
-
I will see what I *can* release without getting scared
Thanks for that! The need isn't quite so acute anymore (since I can use openstreetmap with navit instead now) but it'd still be nice to play around with
-
@pelrun
openstreetmap with navit sounds very interesting. I just visited both homepages. Do you have instructions how to use these maps
with navit. I can't find a ipk file for installing it on my Zaurus.
Thanks for your help in advance :-)
climber
SL-C3100 & pdaXii13v2