Passing an initrd to a Linux kernel with Device Tree

[Dave P Martin]

> -----Original Message-----
> From:
> devicetree-discuss-bounces+dave.martin=arm.com at lists.ozlabs.or
g [mailto:devicetree-discuss-> bounces+dave.martin=arm.com at lists.ozlabs.org] On Behalf Of
> Grant Likely
> Sent: 20 September 2011 21:11
> To: Olivier Martin
> Cc: devicetree-discuss at lists.ozlabs.org
> Subject: Re: Passing an initrd to a Linux kernel with Device Tree
>
> 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.

What does "end address" mean here?

It could be read as meaning either:

a) address of the the final byte of the image
b) address of the first byte following the image (0 if the image ends at 4G)

Cheers
---Dave

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.