From: Sascha Hauer <s.hauer@pengutronix.de>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Changing the baudrate via barebox prompt
Date: Wed, 14 May 2014 09:20:02 +0200 [thread overview]
Message-ID: <20140514072002.GZ5858@pengutronix.de> (raw)
In-Reply-To: <CAOpc7mGG+BLF+Jc1Q3UsSa+R7f96FxS3Rd22mckvJsMq_8m=nA@mail.gmail.com>
On Wed, May 14, 2014 at 08:09:00AM +0200, Holger Schurig wrote:
> Hmm, any reason why csX.baudrate isn't listed under magicvars ?
These variables predate the magicvar support and nobody has ever added
it them to magicvar. It's not clear how we want to add these. Do we want
to add wildcards to the magicvar description (csX)? This gets incorrect
for some devices which can show up as mmcX or mciX depending on the way
they are registered. We could also attach the description to the device
parameter themselves which means we get descriptions for all parameters
actually registered, like
cs0.baudrate Baudrate for the serial console
cs1.baudrate Baudrate for the serial console
...
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-05-14 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 3:34 Fabio Estevam
2014-05-14 4:59 ` Kevin Du Huanpeng
2014-05-14 5:32 ` Antony Pavlov
2014-05-14 6:09 ` Holger Schurig
2014-05-14 7:20 ` Sascha Hauer [this message]
2014-05-14 8:01 ` Holger Schurig
2014-05-14 8:10 ` Holger Schurig
2014-05-14 8:16 ` Sascha Hauer
2014-05-14 12:32 ` Fabio Estevam
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=20140514072002.GZ5858@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=holgerschurig@gmail.com \
/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