linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@genband.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: recommended method of netbooting kernel/dtb in u-boot?
Date: Thu, 11 Apr 2013 12:39:00 -0600	[thread overview]
Message-ID: <51670344.2090101@genband.com> (raw)
In-Reply-To: <3B81A930-A4AB-4AA7-BC36-FCCE55D33C66@kernel.crashing.org>

On 04/11/2013 12:12 PM, Kumar Gala wrote:
>
> On Apr 11, 2013, at 10:44 AM, Chris Friesen wrote:
>
>>
>> Hi all,
>>
>> We've got a powerpc system that uses u-boot.  In our environment on
>> bootup u-boot does a DHCP to get networking info, then uses TFTP to
>> get the kernel, which then does DHCP again and NFS-mounts the
>> initial root filesystem.
>>
>> What's the standard practice for this sort of thing when using
>> device tree blobs?  Do most people use multi-file images or do they
>> TFTP scripts to load and execute separate kernel/dtb files?
>
> We've normally just done multiple tftp fetches and one grabs dtb and
> one grabs kernel.

Do you hardcode the path to the file in the firmware?  Or do you upload 
a script that knows the path to the file?

In our case the path to the boot file(s) depends on which slot the card 
being booted has been inserted in.  The DHCP server knows what the path 
is, so it can set dhcpd.conf appropriately, but we need to get that 
information to the firmware on the card being booted.

Chris

  reply	other threads:[~2013-04-11 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 15:44 recommended method of netbooting kernel/dtb in u-boot? Chris Friesen
2013-04-11 18:12 ` Kumar Gala
2013-04-11 18:39   ` Chris Friesen [this message]
2013-04-11 19:50     ` Ira W. Snyder
2013-04-11 19:59       ` Chris Friesen

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=51670344.2090101@genband.com \
    --to=chris.friesen@genband.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@lists.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;
as well as URLs for NNTP newsgroup(s).