LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Linn <John.Linn@xilinx.com>
To: <linuxppc-dev@ozlabs.org>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: initrd problem with device tree
Date: Wed, 9 Jul 2008 16:10:15 -0600	[thread overview]
Message-ID: <20080709221017.395E0858050@mail185-sin.bigfish.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]

I realize I'm asking below about u-boot, but I'm really trying to better
understand how initrd should work with device trees.  I have also posted
a question to the u-boot user group.

 

When I build the device tree blob into the kernel image and load the
kernel image with my probe, it finds the initrd fine just using
root=/dev/ram and with the kernel configured properly.

 

With the same kernel configuration, when I run with u-boot, the only way
for the kernel to find the initrd is to put linux,initrd-start and
initrd-end in my device tree. I found these items in an old patch from
David Gibson and I'm not sure if or when they should be used.

 

I also notice in booting-without-of.txt, off_mem_rsvmap, but it's not
clear if and how I should be using it to help the problem.

 

Thanks,

John

 

 



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


[-- Attachment #2: Type: text/html, Size: 8856 bytes --]

                 reply	other threads:[~2008-07-09 22:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080709221017.395E0858050@mail185-sin.bigfish.com \
    --to=john.linn@xilinx.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.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