From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from SG2EHSOBE001.bigfish.com (outbound-sin.frontbridge.com [207.46.51.80]) by ozlabs.org (Postfix) with ESMTP id EC56BDDF75 for ; Thu, 10 Jul 2008 08:10:22 +1000 (EST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8E210.90B6D91B" Subject: initrd problem with device tree Date: Wed, 9 Jul 2008 16:10:15 -0600 From: John Linn To: Message-ID: <20080709221017.395E0858050@mail185-sin.bigfish.com> Cc: David Gibson List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------_=_NextPart_001_01C8E210.90B6D91B Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable 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=3D/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 r= ecipient(s) and contain(s) confidential information that may be proprietary= , privileged or copyrighted under applicable law. If you are not the intend= ed recipient, do not read, copy, or forward this email message or any attac= hments. Delete this email message and any attachments immediately. ------_=_NextPart_001_01C8E210.90B6D91B Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable =

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 al= so posted a question to the u-boot user group.

When I build the device tree blob into the kernel image and load the kernel imag= e with my probe, it finds the initrd fine just using root=3D/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= 217;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 c= lear if and how I should be using it to help the problem.

Thanks,

John

This email and any attachments are intended for the sole u= se of the named recipient(s) and contain(s) confidential information that m= ay be proprietary, privileged or copyrighted under applicable law. If you a= re not the intended recipient, do not read, copy, or forward this email mes= sage or any attachments. Delete this email message and any attachments imme= diately. ------_=_NextPart_001_01C8E210.90B6D91B--