Hi Peter,<div><br></div><div>Thanks for your information,</div><div><br></div><div>And can you kindly suggest me,</div><div>1)How the probe will be called by comparing the name in driver and name given in board-files, or it will called based id_table which we fill for particular bus of that driver.</div>
<div>2)How the priority will be followed to call the drivers files like BT first and then HDMI driver.</div><div><br></div><div>Thanks And Regards,</div><div>Ranganath.T.M </div><div><br><div class="gmail_quote">On Wed, Feb 6, 2013 at 8:03 AM, Peter Teoh <span dir="ltr"><<a href="mailto:htmldeveloper@gmail.com" target="_blank">htmldeveloper@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="http://duartes.org/gustavo/blog/post/how-computers-boot-up" target="_blank">http://duartes.org/gustavo/blog/post/how-computers-boot-up</a><div>
<br></div><div>this is for x86, not for ARM though.<div><div class="h5"><br><br><div class="gmail_quote">On Wed, Feb 6, 2013 at 10:30 AM, Peter Teoh <span dir="ltr"><<a href="mailto:htmldeveloper@gmail.com" target="_blank">htmldeveloper@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>normally in embedded uboot is the bootloader. and to trace this is simple:<div><br></div><div>a. understand how uboot works - and this is highly platform specific (uboot is highly hardware dependent)...and examine the point where control passed is passed to kernel image file (which still run at 16 bit real mode), and from there u can trace everything.</div>
<div><br></div><div>b. well u need assembly, as everything starting is written in assembly. for ARM (as u asked for Android), the place is "start_kernel" inside:</div><div><br></div><div>arch/arm/kernel/head-common.S</div>
<div><br></div><div>and then u must learn linker scripting (for ARM is arm/kernel/vmlinux.ld.S) as well, that is how u tell the compiler to generate a image that can be loaded directly into memory and executed directly on the hardware in memory - using the hardware-specific reset vector as the starting point. there is no loader at this stage to load the binary. (uboot will load it as a image, but executeable).</div>
<div><br></div><div>the rest is yours...</div><div><br><div class="gmail_quote"><div><div>On Mon, Feb 4, 2013 at 12:34 PM, Ranganath T.M <span dir="ltr"><<a href="mailto:ranganathtm88@gmail.com" target="_blank">ranganathtm88@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Hi All,<div><br></div><div>I am trying to find out how the kernel will <b>start</b> from the uboot and how the kernel will call there respective static modules which are built as <b>.o</b> file and also how the <b>probe</b> of every modules will be called.</div>
<div><br></div><div>Thanks And Regards</div><span><font color="#888888"><div>Ranganath </div>
</font></span><br></div></div>_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org" target="_blank">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
<br></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br>Regards,<br>Peter Teoh
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br>Regards,<br>Peter Teoh
</font></span></div>
</blockquote></div><br></div>