From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Document the format of the console environment variable
Date: Mon, 30 Mar 2015 09:06:10 +0200 [thread overview]
Message-ID: <5518F5E2.4010803@redhat.com> (raw)
In-Reply-To: <1427644521-13421-1-git-send-email-merker@debian.org>
Hi,
On 29-03-15 17:55, Karsten Merker wrote:
> config_distro_bootcmd.h defines a common boot environment for
> multiple platforms. Document the format of the console
> environment variable to allow the use of generic boot scripts
> on all supported platforms.
>
> Signed-off-by: Karsten Merker <merker@debian.org>
Maybe add something that distros are not encouraged to use this ?
At least on Fedora we do not want to use it, as adding
console=${console} to bootargs on systems with both video-output
(e.g. hdmi out) and a serial port will cause boot messages to
only be shown on the serial port as that is where the /dev/console
then points.
Whereas when using the devicetree chosen/stdout-path property (which
can be set either by u-boot or in the dts with the kernel),
the kernel will use both /dev/tty0 (so the hdmi out) and the serial
port pointed to by chosen/stdout as console, showing boot messages
on both, and systemd will still automatically spawn a getty on the
serial console.
Regards,
Hans
> ---
> doc/README.distro | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/doc/README.distro b/doc/README.distro
> index 0308a4c..3f7ee85 100644
> --- a/doc/README.distro
> +++ b/doc/README.distro
> @@ -201,6 +201,15 @@ variables be set. Default values for these variables are often hard-coded into
> CONFIG_EXTRA_ENV_SETTINGS in the board's U-Boot configuration file, so that
> the user doesn't have to configure them.
>
> +console:
> +
> + Mandatory. The default console device to be passed to the Linux kernel.
> +
> + The console device is specified in accordance with the guidelines
> + described in Documentation/serial-console.txt in the Linux kernel sources.
> + If the device is a serial port, the console variable must specify the
> + console baudrate in addition to the console device, e.g. "ttyS0,115200".
> +
> fdt_addr:
>
> Mandatory for any system that provides the DTB in HW (e.g. ROM) and wishes
>
next prev parent reply other threads:[~2015-03-30 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 1:24 [U-Boot] [PATCH] arm: imx: Switch Wandboard to use config_distro_bootcmd.h Vagrant Cascadian
[not found] ` <20150328131538.GG5034@excalibur.cnev.de>
2015-03-29 13:05 ` Tom Rini
2015-03-29 15:55 ` [U-Boot] [PATCH] Document the format of the console environment variable Karsten Merker
2015-03-30 7:06 ` Hans de Goede [this message]
2015-05-19 15:23 ` [U-Boot] [PATCH] arm: imx: Switch Wandboard to use config_distro_bootcmd.h XoD
2015-05-19 20:42 ` Vagrant Cascadian
2015-05-20 7:36 ` XoD
2015-06-26 11:54 ` XoD
2015-06-26 17:44 ` Nikolay Dimitrov
2015-06-26 19:15 ` XoD
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=5518F5E2.4010803@redhat.com \
--to=hdegoede@redhat.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