Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Stefano Babic <sbabic@denx.de>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V3] u-boot-fw-utils: Add support for libubootenv
Date: Fri, 3 Jan 2020 12:05:49 +0100	[thread overview]
Message-ID: <0619cd66-1a7e-78a2-964d-8bafdc97e025@denx.de> (raw)
In-Reply-To: <67936cf2c289480b0a9b94b7ca52ba2e061c0fad.camel@linuxfoundation.org>

Hi Richard,

On 03/01/20 11:40, Richard Purdie wrote:
> 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? 

Frankly speaking, yes. The topic was discussed more as a year ago on
U-Boot's ML, and libubootenv is the result of this (long) discussion:

	http://u-boot.10912.n7.nabble.com/SWUpdate-U-Boot-environment-library-dependency-tt340530.html#none

One of the major goal is to solve the fragile connection between u-boot
and u-boot-fw-utils. The need to syncronize u-boot with u-boot-fw-utils
has always been a pitfall, specially when projects sets a custom BSP
layer replacing U-Boot with a custom recipe, and then people wonder why
board is bricked. Licensing (LGPL2.1 instead of GPLv2) is another major
goal, too, that libubootenv solves.

> Should we remove the other recipe?

libubootenv is thought to be full compatible with u-boot-fw-utils, and
it was already pushed in many projects. So yes, my proposal and final
goal is then to drop u-boot-fw-utils.

Anyway, I do not know if you prefer to have a "transition" time with
both recipes or it is fine for you to drop soon u-boot-fw-utils.

Best regards,
Stefano

-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================


  reply	other threads:[~2020-01-03 11:05 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
2020-01-03 11:05   ` Stefano Babic [this message]
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=0619cd66-1a7e-78a2-964d-8bafdc97e025@denx.de \
    --to=sbabic@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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