Devicetree
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Olivier Martin <olivier.martin-5wv7dgnIgG8@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: Passing an initrd to a Linux kernel with Device Tree
Date: Tue, 20 Sep 2011 14:10:58 -0600	[thread overview]
Message-ID: <20110920201058.GM7781@ponder.secretlab.ca> (raw)
In-Reply-To: <4e78d3aa.21b0ec0a.63e9.1591SMTPIN_ADDED-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>

On Tue, Sep 20, 2011 at 06:46:22PM +0100, Olivier Martin wrote:
> Hello,
> 
> I tried recently to add support in UEFI to pass an initrd with FDT to a
> Linux kernel. I have searched the Internet but I did not find any
> information to do that.
> 
> FYI, this is the way it is done in ATAG:
> typedef struct {
>   UINT32  start;
>   UINT32  size;
> } LINUX_ATAG_INITRD2;
> 
> The boot loader loads the initrd in system memory and passes the memory
> region information through ATAG.
> 
> 
> Sorry, if it is the wrong mailing-list. In this case, can someone point me
> on the right forum for any Linux FDT oriented questions.

Hmmm, it may not be documented (the binding was implemented a long
time ago before we got strict about documenting bindings).  The magic
is two properties in the /chosen node; "linux,initrd-start" and
"linux,initrd-end".  Each contains the physical start and end
addresses of the initrd.

g.

       reply	other threads:[~2011-09-20 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4e78d3aa.21b0ec0a.63e9.1591SMTPIN_ADDED@mx.google.com>
     [not found] ` <4e78d3aa.21b0ec0a.63e9.1591SMTPIN_ADDED-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2011-09-20 20:10   ` Grant Likely [this message]
     [not found]     ` <20110920201058.GM7781-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-09-21  9:35       ` Passing an initrd to a Linux kernel with Device Tree Dave P Martin
     [not found]         ` <3A52818B08EC2744B4FE79467451246180DF6E9E12-x8AJ9SVuP1o/DnoT/0QEu0EOCMrvLtNR@public.gmane.org>
2011-09-21 14:25           ` Nicolas Pitre
     [not found]             ` <alpine.LFD.2.00.1109210957050.12663-QuJgVwGFrdf/9pzu0YdTqQ@public.gmane.org>
2011-09-21 14:38               ` Grant Likely
2011-09-20 17:46 Olivier Martin

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=20110920201058.GM7781@ponder.secretlab.ca \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=olivier.martin-5wv7dgnIgG8@public.gmane.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