public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V4] add README.distro file
Date: Tue, 20 Jan 2015 09:00:22 +0000	[thread overview]
Message-ID: <1421744422.13341.93.camel@hellion.org.uk> (raw)
In-Reply-To: <1421690104-11204-1-git-send-email-swarren@wwwdotorg.org>

On Mon, 2015-01-19 at 10:55 -0700, Stephen Warren wrote:
> * Indicate that boot.scr is fully supported, not a legacy option.
>   Still, recommend use of extlinux.conf over boot.scr.

Thanks for this. The bits around that look fine now.

One thing I happened to spot while skimming:

> +handled by U-Boot's "syslinux" (disk) or "pxe boot" (network). This is roughly
> +as specified at:
> +
> +http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/
> +
> +... with the exceptions that:
> +
> +* That document prescribes a separate configuration per boot menu option,
> +  whereas U-Boot lumps all options into a single extlinux.conf file. Hence,
> +  U-Boot searches for /extlinux/extlinux.conf then
> +  /boot/extlinux/extlinux.conf on disk, or pxelinux.cfg/default over the
> +  network.
> +
> +* Does not document the fdtdir option, which automatically selects the DTB to
> +  pass to the kernel.

This second bullet doesn't work, either in isolation or when combined
with the sentence fragment which introduces the list. Perhaps the first
few words of the first bullet should be moved to the intro fragment,
e.g. "with the exception that the BootLoaderSpec document:

  * prescribes a sep...
  * does not document ...
"
?

Ian.

      reply	other threads:[~2015-01-20  9:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 17:55 [U-Boot] [PATCH V4] add README.distro file Stephen Warren
2015-01-20  9:00 ` Ian Campbell [this message]

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=1421744422.13341.93.camel@hellion.org.uk \
    --to=ijc@hellion.org.uk \
    --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