<div dir="ltr">Hi Dave.<div>Ok<br><div style>Can you tell me which thing runs faster ?</div></div><div style>1)Copy <b>zImage(compressed kernel)</b> from flash to Ram, jump to start, Relocate compress kernel, uncompress it...</div>
<div style>2)Copy<b> Image(uncompressed one) </b>from flash to RAM and run it right away...</div><div style><br></div><div style>My gut feeling says second one is better, thats what i m trying to prove here... :)</div><div style>
<br></div><div style>Thanks</div><div style>Sandeep.</div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 30, 2013 at 5:55 PM, Dave Hylands <span dir="ltr"><<a href="mailto:dhylands@gmail.com" target="_blank">dhylands@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hey sandeep,<div><div class="h5"><br><br><br>On Wed, Jan 30, 2013 at 5:30 PM, sandeep kumar <<a href="mailto:coolsandyforyou@gmail.com" target="_blank">coolsandyforyou@gmail.com</a>> wrote:<br>
><br>> Hi All<br>> On ARM, Just for learning i am working on booting with uncompressed kernel.<br>
><br>> I am meddling with arch/arm/boot/compressed/head.S, and understand the relocation/decompression stuff through putting some logs.<br>><br>> I want to check how much time it takes for kernel to relocate itself and how much time it takes to decompress etc.,<br>
><br>> Is there any possibility of seeing the current time stamp here, like a register which keeps on counting immediately after boot..<br><br></div></div></div>You're essentially running at the bootloader level here. You haven't started the kernel so the only timers that you have are whatever your bootloader has setup, or whatever you want to setup yourself (bare-metal programming here).<br>
<div><br>--<br>Dave Hylands<br>Shuswap, BC, Canada<br><a href="http://www.davehylands.com" target="_blank">http://www.davehylands.com</a></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>With regards,<br>Sandeep Kumar Anantapalli,<br>
</div>