From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: Denis OSTERLAND <denis.osterland@diehl.com>
Cc: "ada@thorsis.com" <ada@thorsis.com>,
"m.olbrich@pengutronix.de" <m.olbrich@pengutronix.de>,
"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>,
"bth@kamstrup.com" <bth@kamstrup.com>
Subject: Re: [ptxdist] [PATCH v2] u-boot: generate environment image
Date: Mon, 18 Nov 2019 13:25:39 +0100 [thread overview]
Message-ID: <CAH+2xPBKMZsWL33EFk1u2s=qee6eE90tiPVFAF_dsZ54vR_NAA@mail.gmail.com> (raw)
In-Reply-To: <f14b33d92fe457e6d5749b90a2bc621b0f6ff149.camel@diehl.com>
Hi
Den man. 18. nov. 2019 kl. 09.43 skrev Denis OSTERLAND
<denis.osterland@diehl.com>:
>
> Hi,
>
> Am Freitag, den 15.11.2019, 14:59 +0100 schrieb Michael Olbrich:
> > On Wed, Nov 13, 2019 at 06:05:59PM +0100, Bruno Thomsen wrote:
> ...
> > > +config U_BOOT_DEFAULT_ENV_IMAGE_FILE
> > > + prompt "Default environment image filename"
> > > + string
> > > + default "u-boot-env.img"
> > > + help
> > > + Change default environment output image name.
> >
> > Why the custom name? It's just the filename in images/ and it can be
> > changed wenn it's added to an image, if that's necessary.
> > If it's important, then the option should depend on
> > U_BOOT_DEFAULT_ENV_IMAGE
So it's easier to tell what environment image you flashing.
We use the image directly from images/ and does not create a
combined device image, but will remove both image names in
next version.
> > Denis, I think you were asking for a selectable input file, not generating
> > multiple env images?
> correct.
> I see no reason to have both files, or to specify the output file name.
> My suggestion was to give a filename or generate it via get_default_envs.sh if none given.
> If you want to be more explicit, I would prefer a choice between default and custom,
> where the filename depends on the custom selected.
I just overdid the function and will revert it to a simple choice between
none, default and custom.
> > And the same issue as above, if this stays: do we need to custom output
> > filename and hide the suboptions with 'depends'.
Will hide custom source file when choice is none or default.
/Bruno
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-11-18 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 17:05 Bruno Thomsen
2019-11-13 19:02 ` Alexander Dahl
2019-11-15 13:59 ` Michael Olbrich
2019-11-18 8:43 ` Denis OSTERLAND
2019-11-18 12:25 ` Bruno Thomsen [this message]
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='CAH+2xPBKMZsWL33EFk1u2s=qee6eE90tiPVFAF_dsZ54vR_NAA@mail.gmail.com' \
--to=bruno.thomsen@gmail.com \
--cc=ada@thorsis.com \
--cc=bth@kamstrup.com \
--cc=denis.osterland@diehl.com \
--cc=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