View Single Post
Old 12-01-2012, 04:43 AM   #4
giorgio130
Time Waster
giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.giorgio130 ought to be getting tired of karma fortunes by now.
 
Posts: 422
Karma: 289160
Join Date: May 2011
Device: Kobo Glo and Aura HD
Quote:
Originally Posted by eureka View Post
Size of flashed image in fastboot mode on newer Kindles is limited by RAM size only (minus some MB for U-Boot itself and system buffers). But, for example, KT has 256MB RAM and KT's rootfs on system partition (/dev/mmcblk0p1) is about 340MB: that's why rootfs image can be flashed in fastboot mode only partially. It's understandable limitation inherited from standard fastboot.

So, to clarify things, you can't just "remove" size limitation. You'll need to implement new fastboot command for "chunked" downloading and flashing of "big" images. And change fastboot tool to support this new command.
Thanks for the explanation, I couldn't find the cause anywhere. But I actually think that android phones don't have this kind of limitation... Or maybe they just keep their partition size under the amount of available ram?
I'll do some research. BTW, do you know if the limit of 72 kb for the first-stage u-boot applies even to the kindle 3? I didn't find any reference to a "bist" u-boot on this platform, so I'd assume no...
giorgio130 is offline   Reply With Quote