From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] pxe: implement fdtdir extlinux.conf tag
Date: Fri, 24 Jan 2014 10:20:16 -0700 [thread overview]
Message-ID: <52E2A0D0.3060704@wwwdotorg.org> (raw)
In-Reply-To: <20140124161526.GQ3277@bill-the-cat>
On 01/24/2014 09:15 AM, Tom Rini wrote:
> On Thu, Jan 23, 2014 at 12:55:27PM -0700, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> People who write (or scripts that auto-generate) extlinux.conf don't
>> want to know about HW-specific information such as FDT filenames. Create
>> a new extlinux.conf tag "fdtdir" that specifies only the directory where
>> FDT files are located, and defer all knowledge of the filename to U-Boot.
>> The algorithm implemented is:
...
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>
> My only real concern is that
> http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/ is as
> best I can see the spec for extlinux.conf and it doesn't talk about this
> tag. So while it sounds like a good idea, if we implement it and it's
> not documented outside of U-Boot, will anyone use it?
Well, Dennis is actively working on making Fedora support extlinux.conf
for at least ARM, and said on IRC that he was going to patch the Fedora
generator to use it, so yes:-)
Dennis, should you or I simply edit that wiki, or is there some other
process for changing it?
Related, I notice that it documents a "devicetree" tag, whereas U-Boot
(prior to my patches) actually implements an "fdt" tag for the same
purpose...
next prev parent reply other threads:[~2014-01-24 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 19:55 [U-Boot] [PATCH] pxe: implement fdtdir extlinux.conf tag Stephen Warren
2014-01-24 16:15 ` Tom Rini
2014-01-24 17:20 ` Stephen Warren [this message]
2014-01-24 18:23 ` Dennis Gilmore
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=52E2A0D0.3060704@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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