This has nothing to do with this list. On Mon, Aug 22, 2011 at 4:54 AM, NilesH <[email protected]> wrote: > I actually referred a paper and the summary of the idea is a follows > > Fast boot is essential for consumer devices in automotive, medical and > entertainment markets. I describe an efficient bootloader design and > explain how to optimally configure Android’s Linux based kernel for > embedded systems. The basic idea to detail Android userspace design > changes to reach the home screen quickly and allow users to execute > crucial applications first. > > BASIC IDEA: > In embedded systems, existing bootloaders run in three stages. But the > main focus should be on the vendor bootloader and the third stage > bootloader. U-boot and Barebox are examples of third stage bootloaders > that provide a rich set of features. It propose to eliminate the third > stage bootloader by combining its essential features into the vendor > bootloader, creating a single stage bootloader. The single stage > bootloader is small enough to run in the SRAM of 14KB on our setup and > its design constructs are as follows: > # Add capability to load kernel from non-volatile memory. U-Boot or > Barebox only duplicates these activities. > # Configure only those hardware devices that are genuinely > indispensible for system startup such as > system clock setting, RAM initialization, and configuration of NAND. > # System clock should be set to highest possible stable > > I FEEL TO USE COMPRESSED IMAGE. BECAUSE THE EXISTING U-BOOT LOADER HAS > LZMA COMPRESSION/DECOMPRESSION TECHNIQUE AND THERE'S A SLIGHTLY > IMPROVED NEW COMPRESSION/DECOMPRESSION TECHNIQUE CALLED XZ TECHNIQUE. > > > WE FIRST NEED TO MAINLINE THAT .XZ technique IN U BOOT LOADER AND USE > COMPRESSED IMAGE OF KERNEL. > > I also feel to remove some modules that take much time to load and are > not necessary at the boot time. Reducing kernel size will shorten the > load time of kernel from slow non-volatile memory. > > > Other than XZ we can also use other technique that uncompresses image > fast.. > > I heard that mainlining the Bootloaders is not allowed. > Please can somebody help me with this... > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en >
-- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in Oslo: http://bit.ly/fjBo24 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
