From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Stefano Babic <sbabic@denx.de>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V3] u-boot-fw-utils: Add support for libubootenv
Date: Fri, 03 Jan 2020 10:40:23 +0000 [thread overview]
Message-ID: <67936cf2c289480b0a9b94b7ca52ba2e061c0fad.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200103101536.2561-1-sbabic@denx.de>
On Fri, 2020-01-03 at 11:15 +0100, Stefano Babic wrote:
> libubootenv is a replacement for u-boot-fw-utils. It is
> hardware-independent and provides fw_printenv and fw_setenv tools
> that
> are full compatible with the ones provided by U-Boot. A library is
> provided to access the environment from an own application.
> License is LGPL-2.1 and this allow to link the library to proprietary
> code. The user of the tools should install the configuration file
> "fw_env.config", as he is already used to with u-boot-fw-utils. The
> configuration file is compatible with u-boot-fw-utils.
>
> +PROVIDES += "u-boot-fw-utils"
> +RPROVIDES_${PN} += "u-boot-fw-utils"
What is the ultimate intention/end goal here? Does this replace u-boot-
fw-utils? Should we remove the other recipe?
Cheers,
Richard
next prev parent reply other threads:[~2020-01-03 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 10:15 [PATCH V3] u-boot-fw-utils: Add support for libubootenv Stefano Babic
2020-01-03 10:40 ` Richard Purdie [this message]
2020-01-03 11:05 ` Stefano Babic
2020-01-03 11:18 ` Richard Purdie
2020-01-03 12:23 ` 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=67936cf2c289480b0a9b94b7ca52ba2e061c0fad.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sbabic@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;
as well as URLs for NNTP newsgroup(s).