From: Wolfgang Denk <wd@denx.de>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v5 2/5] doc: Move environment documentation to rST
Date: Mon, 04 Oct 2021 14:05:33 +0200 [thread overview]
Message-ID: <2672853.1633349133@gemini.denx.de> (raw)
In-Reply-To: <20211002003848.1803446-3-sjg@chromium.org>
Dear Simon,
In message <20211002003848.1803446-3-sjg@chromium.org> you wrote:
>
> +baudrate
> + see CONFIG_BAUDRATE
> +
> +bootdelay
> + see CONFIG_BOOTDELAY
> +
> +bootcmd
> + see CONFIG_BOOTCOMMAND
I know you only copied this, but the text is actually not helpful,
as it does not even mention where to look for documentation for
these CONFIG_* options
> +autoload
> + if set to "no" (any string beginning with 'n'),
> + "bootp" will just load perform a lookup of the
> + configuration from the BOOTP server, but not try to
> + load any image using TFTP
We should add "dhcp" here, too.
> +autostart
> + if set to "yes", an image loaded using the "bootp",
> + "rarpboot", "tftpboot" or "diskboot" commands will
> + be automatically started (by internally calling
> + "bootm")
> +
> + If set to "no", a standalone image passed to the
> + "bootm" command will be copied to the load address
> + (and eventually uncompressed), but NOT be started.
> + This can be used to load and uncompress arbitrary
> + data.
There is a consistency problem here.
In "bootm" (cmd/bootm.c), the "yes" part applies - any other value
or the variable not being defined omitting the call of do_bootm().
This also applies to nandboot, btw.
In "bootelf" (cmd/elf.c), the "no" part applies - any other value or
the variable not being defined will cause do_bootelf_exec() to be
called.
This should be both documented and fixed.
> +ipaddr
> + IP address; needed for tftpboot command
...and for ping etc.
> +vlan
> + When set to a value < 4095 the traffic over
> + Ethernet is encapsulated/received over 802.1q
> + VLAN tagged frames.
Really? I can't see where "vlan" is actually used in the code.
[I looked for it because I could not remember if the values is
interpreted as decimal or hex number...]
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Systems programmers are the high priests of a low cult.
-- R.S. Barton
next prev parent reply other threads:[~2021-10-04 12:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 0:38 [PATCH v5 0/5] env: Allow environment in text files Simon Glass
2021-10-02 0:38 ` [PATCH v5 1/5] sandbox: Drop distro_boot Simon Glass
2021-10-02 0:38 ` [PATCH v5 2/5] doc: Move environment documentation to rST Simon Glass
2021-10-04 12:05 ` Wolfgang Denk [this message]
2021-10-02 0:38 ` [PATCH v5 3/5] env: Allow U-Boot scripts to be placed in a .env file Simon Glass
2021-10-04 7:28 ` Rasmus Villemoes
2021-10-04 15:38 ` Tom Rini
2021-10-05 14:42 ` Simon Glass
2021-10-04 12:08 ` Wolfgang Denk
2021-10-05 14:42 ` Simon Glass
2021-10-05 14:55 ` Wolfgang Denk
2021-10-05 15:33 ` Simon Glass
2021-10-05 15:52 ` Tom Rini
2021-10-05 17:27 ` Simon Glass
2021-10-06 7:08 ` Wolfgang Denk
2021-10-02 0:38 ` [PATCH v5 4/5] env: Allow environment files to use the C preprocessor Simon Glass
2021-10-04 12:12 ` Wolfgang Denk
2021-10-02 0:38 ` [PATCH v5 5/5] sandbox: Use a text-based environment Simon Glass
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=2672853.1633349133@gemini.denx.de \
--to=wd@denx.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.