Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Alex <baggerml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: kernel booting and params
Date: Wed, 27 Jan 2010 16:46:45 +0300	[thread overview]
Message-ID: <4B6043C5.1050809@gmail.com> (raw)
In-Reply-To: <4B6040C6.2020501@mlbassoc.com>

Gary Thomas wrote:
> On 01/27/2010 06:10 AM, Alex wrote:
>> Gary Thomas wrote:
>>> On 01/27/2010 06:03 AM, Alex wrote:
>>>> Hello everyone!
>>>>
>>>> Trying to find information about kernel booting gave me nothing so 
>>>> I decided to write here.
>>>>
>>>> The question is: how does linux kernel know where to get its 
>>>> parameters' string? To be more precise, what actions in general 
>>>> should a linux bootloader do to tell the kernel its
>>>> params and boot it?
>>>>
>>>> ...
>>>
>>> This process is different for every architecture (x86, arm, powerpc, 
>>> ...)
>>>
>>> What platform(s) are you trying to understand?
>>
>> It is an arm cpu. The platform is dm6446.
>
> n.b. replies should be on the mailing list so that all benefit.

Oh, sorry for that =(

>
> The information for ARM is passed in memory at a fixed block with
> pointers and tags describing the various data.  The Linux source
> file '.../arch/arm/include/asm/setup.h' describes how this works.
>
> Look at U-Boot to see how it handles this linkage.

Thanks a lot! I'll look!




      reply	other threads:[~2010-01-27 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 13:03 kernel booting and params Alex
2010-01-27 13:06 ` Gary Thomas
     [not found]   ` <4B603B5F.8080009@gmail.com>
2010-01-27 13:33     ` Gary Thomas
2010-01-27 13:46       ` Alex [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B6043C5.1050809@gmail.com \
    --to=baggerml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox