From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 1/2] board: amarula: Add A64-Relic support
Date: Thu, 1 Nov 2018 13:39:18 +0100 [thread overview]
Message-ID: <20181101133918.43f30a1e@windsurf> (raw)
In-Reply-To: <5400d862-d44e-c5ab-b3e6-b3b68193862e@mind.be>
Hello,
On Thu, 1 Nov 2018 12:59:22 +0100, Arnout Vandecappelle wrote:
> Also it isn't clear to me why the extlinux.conf is needed when we're actually
> using U-Boot, but I guess there must be a reason for it :-)
Yes, that's one of the way U-Boot can now be told how to boot. See
http://git.denx.de/?p=u-boot.git;a=blob;f=doc/README.distro;h=f8e9752a0fa4244ef0a6f7ee530b0aa218080cac;hb=HEAD.
Basically, the idea is that U-Boot simply looks at extlinux.conf in
various well-defined locations in the root filesystem, and this allows
the operating system installed to tell U-Boot how it should be booted.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-01 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 13:03 [Buildroot] [PATCH v6 1/2] board: amarula: Add A64-Relic support Jagan Teki
2018-10-26 13:03 ` [Buildroot] [PATCH v6 2/2] board: amarula: a64-relic: Add WiFi support Jagan Teki
2018-11-01 11:59 ` [Buildroot] [PATCH v6 1/2] board: amarula: Add A64-Relic support Arnout Vandecappelle
2018-11-01 12:39 ` Thomas Petazzoni [this message]
2018-11-01 12:40 ` Thomas Petazzoni
2018-11-01 12:48 ` Baruch Siach
2018-11-01 13:22 ` Thomas Petazzoni
2018-11-03 10:48 ` Jagan Teki
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=20181101133918.43f30a1e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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