mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: Denis OSTERLAND <denis.osterland@diehl.com>
Cc: "ada@thorsis.com" <ada@thorsis.com>,
	"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>,
	"bth@kamstrup.com" <bth@kamstrup.com>
Subject: Re: [ptxdist] [PATCH v4] u-boot: generate environment image
Date: Mon, 25 Nov 2019 13:30:30 +0100	[thread overview]
Message-ID: <CAH+2xPD5WZHBUFvYokVJSp4GDyrYauKP2uiZJfcWPpaKDhqZWQ@mail.gmail.com> (raw)
In-Reply-To: <b0bd5d6a6ff07d016dca70d487226ac247c1855d.camel@diehl.com>

Hi Denis,

Den man. 25. nov. 2019 kl. 09.44 skrev Denis OSTERLAND
<denis.osterland@diehl.com>:
> > +choice
> > +     prompt "Generate environment image"
> > +     default U_BOOT_NONE_ENV_IMAGE
> > +     help
> > +       U-Boot from version 2018.03 support out-of-tree environment
> > +       image generation.
> > +
> > +config U_BOOT_NONE_ENV_IMAGE
> looks a little bit odd.
> I would expect a common prefix, with the choice at the end.
> U_BOOT_ENV_IMAGE_NONE
> U_BOOT_ENV_IMAGE_DEFAULT
> U_BOOT_ENV_IMAGE_CUSTOM
>
> But that´s not a show stopper, I think.

Okay, I see what you mean, a little bit less Yoda :)

> > +ifdef PTXCONF_U_BOOT_DEFAULT_ENV_IMAGE
> > +     $(U_BOOT_MAKE_ENV) $(U_BOOT_DIR)/scripts/get_default_envs.sh $(U_BOOT_BUILD_DIR) | \
> > +             $(U_BOOT_BUILD_DIR)/tools/mkenvimage \
> > +             $(call ptx/ifdef,PTXCONF_U_BOOT_ENV_IMAGE_REDUNDANT,-r,) \
> > +             -s $(PTXCONF_U_BOOT_ENV_IMAGE_SIZE) \
> > +             -o $(U_BOOT_BUILD_DIR)/u-boot-env.img -
> > +endif
> > +ifdef PTXCONF_U_BOOT_CUSTOM_ENV_IMAGE
> > +     $(U_BOOT_BUILD_DIR)/tools/mkenvimage \
> > +             $(call ptx/ifdef,PTXCONF_U_BOOT_ENV_IMAGE_REDUNDANT,-r,) \
> > +             -s $(PTXCONF_U_BOOT_ENV_IMAGE_SIZE) \
> > +             -o $(U_BOOT_BUILD_DIR)/u-boot-custom-env.img \
> I see no need for a different env image name here.
> Custom or default is the choice how to generate the image.
> It is easier to pass the images to your factory if the have always the same name.
> This gives you the chance to change image type, without a need to change production flow.

Check, one image to rule them all.

> > -     @rm -vf $(IMAGEDIR)/u-boot.imx
> > +     @rm -vf $(IMAGEDIR)/u-boot.imx $(IMAGEDIR)/u-boot-dtb.imx
> Why u-boot-dtb.imx sneaks in here? Have i missed something?

My mistake, I will move it to a separate bugfix patch.

/Bruno

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2019-11-25 12:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22 15:42 Bruno Thomsen
2019-11-22 17:36 ` Alexander Dahl
2019-11-25  9:15   ` Denis OSTERLAND
2019-11-25  8:44 ` Denis OSTERLAND
2019-11-25 12:30   ` 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+2xPD5WZHBUFvYokVJSp4GDyrYauKP2uiZJfcWPpaKDhqZWQ@mail.gmail.com \
    --to=bruno.thomsen@gmail.com \
    --cc=ada@thorsis.com \
    --cc=bth@kamstrup.com \
    --cc=denis.osterland@diehl.com \
    --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