From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] tools/env: Support UBI devices
Date: Wed, 1 Jun 2016 07:07:46 +0200 [thread overview]
Message-ID: <574E6DA2.1010406@denx.de> (raw)
In-Reply-To: <1463436437-15254-1-git-send-email-kevin.smith@elecsyscorp.com>
Hello Kevin,
Sorry for the late reply
Am 17.05.2016 um 00:07 schrieb Kevin Smith:
> Instead of requiring gluebi to update u-boot environments from
> Linux, directly support writing to an UBI device. The
> fw_env.config file will look something like this:
>
> Device Offset Envsize LEB Size Count
> /dev/ubi0_0 0 0x10000 0x1f000 1
>
> It is important to use LEB size instead of PEB size when using
> UBI.
>
> Signed-off-by: Kevin Smith <kevin.smith@elecsyscorp.com>
> Cc: Michael Heimpold <mhei@heimpold.de>
> Cc: Joe Hershberger <joe.hershberger@ni.com>
> ---
> tools/env/fw_env.c | 71 ++++++++++++++++++++++++++++++++++++------------------
> 1 file changed, 48 insertions(+), 23 deletions(-)
Did you looked at the patches from Marcin. He also did such an
approach here:
[U-Boot,1/2] tools: env: Fix format warnings in debug
http://patchwork.ozlabs.org/patch/619306/
[U-Boot,2/2] tools: env: Add support for direct read/write UBI volumes
http://patchwork.ozlabs.org/patch/619305/
I like his approach more, as with it we can also use UBI Volumes
by name and the config file looks cleaner to me ...
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2016-06-01 5:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 22:07 [U-Boot] [RFC] tools/env: Support UBI devices Kevin Smith
2016-05-24 15:27 ` Joe Hershberger
2016-06-01 5:07 ` Heiko Schocher [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=574E6DA2.1010406@denx.de \
--to=hs@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.