How the follow Starts in Android-Kernel

[Ritesh Harjani]

Hi all,

Here is a very good link on "*Booting ARM Linux SMP on MPCore*" explained
with little code.

http://www.linux-arm.org/LinuxBootLoader/SMPBoot

Regards
Ritesh


On Wed, Feb 6, 2013 at 10:20 AM, Ranganath T.M <ranganathtm88 at gmail.com>wrote:

> Hi Peter,
>
> Thanks for your information,
>
> And can you kindly suggest me,
> 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.
> 2)How the priority will be followed to call the drivers files like BT
> first and then HDMI driver.
>
> Thanks And Regards,
> Ranganath.T.M
>
> On Wed, Feb 6, 2013 at 8:03 AM, Peter Teoh <htmldeveloper at gmail.com>wrote:
>
>> http://duartes.org/gustavo/blog/post/how-computers-boot-up
>>
>> this is for x86, not for ARM though.
>>
>>
>> On Wed, Feb 6, 2013 at 10:30 AM, Peter Teoh <htmldeveloper at gmail.com>wrote:
>>
>>>
>>> normally in embedded uboot is the bootloader.   and to trace this is
>>> simple:
>>>
>>> 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.
>>>
>>> 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:
>>>
>>> arch/arm/kernel/head-common.S
>>>
>>> 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).
>>>
>>> the rest is yours...
>>>
>>> On Mon, Feb 4, 2013 at 12:34 PM, Ranganath T.M <ranganathtm88 at gmail.com>wrote:
>>>
>>>> Hi All,
>>>>
>>>> I am trying to find out how the kernel will *start* from the uboot and
>>>> how the kernel will call there respective static modules which are built as
>>>> *.o* file and also how the *probe* of every modules will be called.
>>>>
>>>> Thanks And Regards
>>>> Ranganath
>>>>
>>>> _______________________________________________
>>>> Kernelnewbies mailing list
>>>> Kernelnewbies at kernelnewbies.org
>>>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>>>
>>>>
>>>
>>>
>>> --
>>> Regards,
>>> Peter Teoh
>>>
>>
>>
>>
>> --
>> Regards,
>> Peter Teoh
>>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130206/3e28069c/attachment.html