From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH / RFC] replace umkimage by u-boot sources
Date: Sun, 22 Jan 2012 11:14:32 +0100 [thread overview]
Message-ID: <20120122101432.GC12400@pengutronix.de> (raw)
In-Reply-To: <4F1BDDE3.7050807@biessmann.de>
On Sun, Jan 22, 2012 at 10:58:59AM +0100, Andreas Bießmann wrote:
> > I don't know fw_printenv. Please elaborate.
>
> As Bernhard said it is a tool to access u-boot configuration from linux
> through /dev/mtdX, but some target specific configuration is required
> here. So would be some ToDo comment required or just leave this til
> someone stumble over the missing target configuration?
Is this a config file, or what? If yes, add an option for it, and use
install_alternative to install it. Then you can add your target specific
file to your BSP. Or always install and add one to generic/ in ptxdist, if
there are some sane default values.
> I know we will need the fw_printenv tool in some of our products in near
> future but at the moment I just want to have a submenu for U-Boot tools.
> A submenu with just one entry would be a bit empty ...
>
> <snip>
>
> >> --- /dev/null
> >> +++ b/rules/host-u-boot-tools.in
> >> @@ -0,0 +1,8 @@
> >> +## SECTION=hosttools_noprompt
> >> +
> >> +config HOST_U_BOOT_TOOLS
> >> + tristate
> >> + default ALLYES
> >> + help
> >> + the U-Boot tools contains the mkimage command which is used
> >> + to create boot images for the U-Boot bootloader.
> >
> > Can we even see the help for a noprompt option?
>
> I don't know ... it was like this before (in host-umkimage.in).
Remove the help. host-umkimage used to have a prompt and the help was not
removed with it.
Michael
--
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 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-01-22 10:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 16:59 Andreas Bießmann
2012-01-21 18:22 ` Michael Olbrich
2012-01-21 20:08 ` Bernhard Walle
2012-01-22 9:17 ` Michael Olbrich
2012-01-22 9:58 ` Andreas Bießmann
2012-01-22 10:14 ` Michael Olbrich [this message]
2012-01-22 14:49 ` [ptxdist] [PATCH v2] " Andreas Bießmann
2012-01-22 14:57 ` Bernhard Walle
2012-01-23 12:37 ` Andreas Bießmann
2012-01-26 15:06 ` Michael Olbrich
2012-01-26 16:05 ` Andreas Bießmann
2012-01-23 12:40 ` Andreas Bießmann
2012-01-23 13:07 ` Bernhard Walle
2012-01-23 13:16 ` Andreas Bießmann
2012-01-23 13:44 ` Bernhard Walle
2012-01-27 7:17 ` Andreas Bießmann
2012-01-27 23:38 ` [ptxdist] [PATCH v3] " Andreas Bießmann
2012-01-31 14:50 ` Michael Olbrich
2012-01-31 22:49 ` [ptxdist] [PATCH v4] " Andreas Bießmann
2012-02-01 8:55 ` Michael Olbrich
2012-03-12 9:00 ` Andreas Bießmann
2012-03-12 10:46 ` Michael Olbrich
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=20120122101432.GC12400@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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