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 10:16:44 +0200 [thread overview]
Message-ID: <20140514081644.GB5858@pengutronix.de> (raw)
In-Reply-To: <CAOpc7mHnhTLxqA9FABZMSRnf05Ocu99bFTkch1DH63O+7=U-yQ@mail.gmail.com>
On Wed, May 14, 2014 at 10:01:10AM +0200, Holger Schurig wrote:
> Hmm, i thought more that "magicvars" could also iterate over the
> devices and spits out their parameter. Internally, they are different,
> but from a users perspective both things do something "magical": a
> simple setting of a variable does some action.
Right now magicvars is just a compile time generated array of struct
magicvar. We could add a const char *description argument to the
dev_add_param_* functions for adding the descriptions to the parameters.
You can get the available parameters for a device with 'devinfo
<devname>', but currently there is no way to see all available
parameters for all devices. Also there can be no description attached
to a parameter. Adding this would indeed be valuable.
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 8:17 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
2014-05-14 8:01 ` Holger Schurig
2014-05-14 8:10 ` Holger Schurig
2014-05-14 8:16 ` Sascha Hauer [this message]
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=20140514081644.GB5858@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