From: Andreas Reichel <andreas.reichel.ext@siemens.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] SWUpdate - U-Boot environment library dependency
Date: Tue, 4 Sep 2018 12:30:00 +0200 [thread overview]
Message-ID: <20180904102959.GA1766@iiotirae> (raw)
Hi all,
as Stefano Babic was so friendly and pointed out a few things already,
we come the following problematic points:
For SWupdate to access U-Boot's environment, it uses code from U-Boot.
Before 2015, fw_env.c was copied - hence out of version control,
afterwards and since then, a lib.a produced by U-Boot has been used
and renamed to libubootenv.a to link against.
However, this approach creates several difficulties:
* Distros like Debian cannot provide a devel package for SWUpdate like
u-boot-dev, since U-Boot has its default environment code compiled
board-dependently and Debian needed it board-independent.
If a board-independent libubootenv.a was provided without
a specific default environment, the first update process would destroy
the U-Boot environment if it had had bad CRC before.
(Thanks Stefano for this good point).
* If we have a board with U-Boot already preinstalled and want to
compile SWUpdate for it, we need the sources of this very U-Boot to
get the propper lib. For example in a debian-like build system we had to
compile U-Boot again, although it is already installed since we lack
a dev package.
* U-Boot does not provide any default means to install a development
library. Thus anything we modify on-top might break with the next
version.
First proposal by Stefano and me would be to somehow split the default
environment from the library to have a board-independent component and
board specific data that is passed to U-Boot and SWUpdate somehow.
Goal is to factor out U-Boot environment support for other software like
SWUpdate and not patching and hacking like its the case with recipes as in
openembedded atm.
Thanks,
Andreas
--
Andreas Reichel
Dipl.-Phys. (Univ.)
Software Consultant
Andreas.Reichel at tngtech.com, +49-174-3180074
TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring
Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller
Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082
next reply other threads:[~2018-09-04 10:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 10:30 Andreas Reichel [this message]
2018-11-20 21:11 ` [U-Boot] SWUpdate - U-Boot environment library dependency Simon Goldschmidt
2018-11-20 23:10 ` Marek Vasut
2018-11-21 9:10 ` [U-Boot] [swupdate] " Stefano Babic
2018-11-21 9:20 ` Wolfgang Denk
2018-11-21 14:31 ` Marek Vasut
2018-11-21 14:56 ` Stefano Babic
2018-11-21 15:31 ` [U-Boot] " Simon Goldschmidt
2018-11-21 15:34 ` Marek Vasut
2018-11-21 16:23 ` [U-Boot] [swupdate] " Otavio Salvador
2018-11-21 8:31 ` [U-Boot] " Wolfgang Denk
2018-11-21 9:33 ` [U-Boot] [swupdate] " Stefano Babic
2018-11-21 10:14 ` Simon Goldschmidt
2018-11-21 10:22 ` Jan Kiszka
2018-11-21 10:49 ` Stefano Babic
2018-11-21 11:45 ` Wolfgang Denk
2018-11-21 11:56 ` Simon Goldschmidt
2018-11-21 12:22 ` Wolfgang Denk
2018-11-21 13:30 ` Stefano Babic
2018-11-21 14:27 ` Wolfgang Denk
2018-11-21 14:37 ` Simon Goldschmidt
2018-11-21 15:01 ` Stefano Babic
2018-11-21 15:41 ` Wolfgang Denk
2018-11-21 15:48 ` Simon Goldschmidt
2018-11-21 15:56 ` Wolfgang Denk
2018-11-21 17:06 ` Simon Goldschmidt
2018-11-22 14:22 ` Wolfgang Denk
2018-11-22 14:41 ` Simon Goldschmidt
2018-11-22 16:00 ` Wolfgang Denk
2018-11-22 16:05 ` Simon Goldschmidt
2018-11-21 11:38 ` Wolfgang Denk
2018-11-21 13:16 ` Stefano Babic
2018-11-21 14:23 ` Wolfgang Denk
2018-11-21 15:13 ` Simon Goldschmidt
2018-11-21 9:19 ` Stefano Babic
2018-11-21 10:02 ` Jan Kiszka
2018-11-21 10:21 ` Simon Goldschmidt
2018-11-21 11:05 ` Stefano Babic
2018-11-21 11:13 ` Simon Goldschmidt
2018-11-21 11:52 ` Stefano Babic
2019-03-04 16:26 ` Stefano Babic
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=20180904102959.GA1766@iiotirae \
--to=andreas.reichel.ext@siemens.com \
--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