View Single Post
Old 11-11-2011, 04:00 PM   #22
yifanlu
Kindle Dissector
yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.
 
Posts: 662
Karma: 475607
Join Date: Jul 2010
Device: Amazon Kindle 3
Quote:
Originally Posted by giorgio130 View Post
Just as a bottom-up approach is failing what about my initial try? Can't we start debug from there? At least it would boot... I can't really say much from the log I posted though.
So much stuff's changed in terms of binaries, how stuff works, etc, that it would be more pain trying to see why the framework won't boot then trying to see why the kernel won't boot. When "debugging" the kernel/boot process, it is easier as it's open source stuff and linux stuff that is easier to fix then amazon's proprietary Java framework. But you're free to do whatever you want, this is just my opinion.

EDIT: Yup, busybox imports from GLIB_2.11. If we compile the 2.12 set of tools, for the older kernel, we would be set. Amazon was even kind enough to provide us with the source.

Last edited by yifanlu; 11-24-2011 at 01:20 AM.
yifanlu is offline   Reply With Quote