public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@majess.pl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv2] scripts: Add script to extract default environment
Date: Wed, 28 Sep 2016 22:33:43 +0200	[thread overview]
Message-ID: <20160928223343.4eac908d@jawa> (raw)
In-Reply-To: <CAPnjgZ3UoasE_iz562Uw9Rk2QsA+_yRh=3ffNjNSQHc2cq=5-w@mail.gmail.com>

Hi Simon,

> Hi,
> 
> On 27 September 2016 at 07:37, Lukasz Majewski <l.majewski@majess.pl>
> wrote:
> > Hi Simon,
> >
> >> Hi Lukasz,
> >>
> >> On 16 September 2016 at 22:57, Lukasz Majewski
> >> <l.majewski@majess.pl> wrote:
> >> > This script looks for env_common.o object file and extracts from
> >> > it default u-boot environment, which is afterwards printed on
> >> > standard output.
> >> >
> >> > Usage example:
> >> > get_default_envs.sh > u-boot-env-default.txt
> >> >
> >> > The generated text file can be used as input for mkenvimage.
> >> >
> >> > Signed-off-by: Lukasz Majewski <l.majewski@majess.pl>
> >> >
> >> > ---
> >> > Changes for v2:
> >> > - Sort uniquely entries
> >> > - Exclude env_common.o generated for SPL
> >> > ---
> >> >  scripts/get_default_envs.sh | 34
> >> > ++++++++++++++++++++++++++++++++++ 1 file changed, 34
> >> > insertions(+) create mode 100755 scripts/get_default_envs.sh
> >>
> >> Reviewed-by: Simon Glass <sjg@chromium.org>
> >>
> >> But why is this needed?
> >
> > Some boards for production u-boot have all the envs hardcoded in
> > their ./include/configs/<board>.h file.
> >
> > Also, they support envs stored on persistent memory - like eMMC.
> >
> > During flashing both u-boot and envs are stored on the target
> > memory. Such script allows having the same data in both places.
> >
> > I do know that I could also use external file, which I could
> > include to u-boot during compilation and compile the boot.scr file
> > with mkimage.
> >
> > Or maybe there is any other way?
> 
> Seems OK to me, I was just curious.

I was afraid that similar functionality was already provided for e.g.
sandbox :-).

Thanks for review.

Best regards,
?ukasz Majewski

> 
> >
> > Best regards,
> > ?ukasz Majewski
> 
> [...]

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160928/b321f61f/attachment.sig>

  reply	other threads:[~2016-09-28 20:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17  4:57 [U-Boot] [PATCHv2] scripts: Add script to extract default environment Lukasz Majewski
2016-09-27  0:33 ` Simon Glass
2016-09-27 13:37   ` Lukasz Majewski
2016-09-28 15:46     ` Simon Glass
2016-09-28 20:33       ` Lukasz Majewski [this message]
2016-10-08 17:06 ` [U-Boot] [U-Boot, PATCHv2] " Tom Rini

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=20160928223343.4eac908d@jawa \
    --to=l.majewski@majess.pl \
    --cc=u-boot@lists.denx.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