Brian Swetland wrote:
["Woodruff, Richard" <r-woodruff2@xxxxxx>]
Can someone shareing some tips on it ?
Sorry, I don't have many tips. I did find that first simulator
downloads were wrongly accessing the TLS. Therefore that code would
break on 3430 which has a real hardware register.
That's our bad. Not fixed in the M5 SDK, but we will definitely be
making our libc play nice with hardware TLS before 1.0 is final.
Blogs have a lot of info on hack methods. WindRiver has base code so
they can make it work with out hacks if they get some board support
help. Google directly obviously can make it work.
I'm hoping to get a public git repository put together with the
various android-specific kernel patches (binder, logger, alarm drivers,
goldflish platform support, etc) soon. This should at least make
it easier for folks to merge various drivers 'n things into their
working trees, rather than having to extract them from the kernel
source tarball provided with emulator/sdk releases.
This sounds great!
I can't speak for all the other people out there, but I'd like to add
a small "but":
While this will be helpful, extracting what you need from the android
kernel and merging it into an other one isn't such a big issue. You
can do it on the host, you don't need the emulator/sdk for it, there
are tools which can help here used quite often with merging other
trees, so some work but not a really big thing.
But (sorry if I miss anything here) extracting the binary content of
userdata.img and system.img is quite tricky. As already mentioned, I
couldn't find a way to mount the yaffs2 images on host and extract the
content yet. What I currently know is that you have to run the
emulator with sdcard simulation, add a static linked busybox to have
tar inside the emulator, tar the userdata and system directory in
running emulator to sdcard (with maybe getting some temporary user
data in it you may be normally don't need) and then extracting the
content on host mounting fat sdcard image.
In case anybody knows an easier way to access the content of the
yaffs2 images on host, this would be helpful. Else, in a first step,
some easier way to get userdata.img and system.img content would be
helpful.
Many thanks
Dirk
Btw: The best idea regarding extracting content of yaffs2 images I
heard was
http://lists.aleph1.co.uk/lurker/message/20080218.222359.6cc4bd2e.en.html
but seems that I'm not really familiar with this sort of programming ;)
-
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
