From: Alexander Dahl <ada@thorsis.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot and The Boot Loader Specification
Date: Wed, 17 Oct 2018 14:04:00 +0200 [thread overview]
Message-ID: <2092760.TlMJupW03t@ada> (raw)
Hei hei,
while setting up U-Boot for a new board, I read doc/README.distro and tried to
follow it for making things smooth with standard distributions. The document
mentions the so called "Boot Loader Specification" [1] as follows:
> This is roughly
> as specified at:
>
> http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/
>
> ... with the exceptions that the BootLoaderSpec document:
I played with the extlinux.conf format snippets from the U-Boot docs. Upstream
extlinux docs are not really helpful, especially not for options regarding dtb
files. And I tried a config based on the Boot Loader Spec:
Scanning mmc 2:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
366 bytes read in 268 ms (1000 Bytes/s)
Ignoring unknown command: title
Ignoring unknown command: version
Ignoring unknown command: options
Ignoring unknown command: linux
Ignoring unknown command: devicetree
Am I right, U-Boot does not support that spec at all? Files are in different
positions, and the keywords are all different? If so, then the U-Boot
documentation is misleading (and people will be frustrated to follow the hints
given in there).
Are there any plans to support that specification or is anybody working on
that? If not, would a patch be okay to reword that part of the documentation?
Greets
Alex
[1] recent version here: https://systemd.io/BOOT_LOADER_SPECIFICATION
next reply other threads:[~2018-10-17 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 12:04 Alexander Dahl [this message]
2018-10-19 6:53 ` [U-Boot] U-Boot and The Boot Loader Specification Wolfgang Denk
2018-10-19 8:17 ` Alexander Dahl
2018-10-19 9:10 ` Wolfgang Denk
2018-10-19 9:40 ` Alexander Dahl
2018-10-19 10:12 ` Wolfgang Denk
2018-10-25 12:53 ` 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=2092760.TlMJupW03t@ada \
--to=ada@thorsis.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