From: Chris Friesen <chris.friesen@genband.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] recommended method of netbooting kernel/dtb in u-boot?
Date: Thu, 11 Apr 2013 13:01:16 -0600 [thread overview]
Message-ID: <5167087C.8080503@genband.com> (raw)
Hi all,
We've got a Linux powerpc system that uses u-boot. Generally in our
environment on bootup the firmware 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. The paths on the server vary
depending on which slot is being booted, so it's not practical to
hard-code anything in u-boot.
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? Or is there some
other option I'm overlooking?
For multi-part images is there an in-kernel way of generating a file
containing a kernel and dtb combined? I saw a patch proposed in 2008 to
add a uImage.<dt> build target but it was shot down because it used the
legacy multi-file format. Is there an equivalent build target that uses
the FIT format?
Thanks,
Chris
--
Chris Friesen
Software Designer
500 Palladium Drive, Suite 2100
Ottawa, Ontario K2N 1C2, Canada
www.genband.com
office:+1.343.883.2717
chris.friesen at genband.com
reply other threads:[~2013-04-11 19:01 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=5167087C.8080503@genband.com \
--to=chris.friesen@genband.com \
--cc=u-boot@lists.denx.de \
/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