From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marex@denx.de>
Cc: linux-snps-arc@lists.infradead.org,
Alexey Brodkin <alexey.brodkin@synopsys.com>,
Otavio Salvador <otavio@ossystems.com.br>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] u-boot: Add mkenvimage tool
Date: Mon, 19 Nov 2018 14:08:35 -0500 [thread overview]
Message-ID: <20181119190835.GO11247@bill-the-cat> (raw)
In-Reply-To: <1fd9e473-66ba-bbb8-87a9-32bb78e359e3@denx.de>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
On Mon, Nov 19, 2018 at 01:51:41PM +0100, Marek Vasut wrote:
> On 11/19/2018 11:04 AM, Alexey Brodkin wrote:
> > This utility is used for creation of images containing
> > usable in run-time U-Boot environment.
> >
> > As of today this utility is added per-board like here [1]
> > for Intel Edison board.
> >
> > [1] http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-edison/tree/meta-intel-edison-bsp/recipes-bsp/u-boot/u-boot-tools_2014.04.bb
> >
> > Given there're quite some U-Boot tools that we may want to add later
> > this recipe name switch from "u-boot-mkimage" to generic "u-boot-tools"
> > still for compatibility we provide "u-boot-mkimage" with help
> > of PROVIDES as well as proposed "u-boot-mkenvimage".
> >
> > Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> > Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Cc: Otavio Salvador <otavio@ossystems.com.br>
> > Cc: Martin Jansa <martin.jansa@gmail.com>
> > Cc: Ross Burton <ross.burton@intel.com>
> > Cc: Marek Vasut <marex@denx.de>
>
> Do we want to generate one package per tool or not ?
I think so, yes. Not all places will want all tools.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2018-11-19 19:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 10:04 [PATCH v3] u-boot: Add mkenvimage tool Alexey Brodkin
2018-11-19 12:51 ` Marek Vasut
2018-11-19 19:08 ` Tom Rini [this message]
2018-11-19 19:22 ` Otavio Salvador
2018-11-19 19:47 ` Alexey Brodkin
2018-11-20 14:29 ` Peter Kjellerstedt
2018-11-20 15:39 ` Burton, Ross
2018-11-20 15:40 ` Burton, Ross
2018-11-20 15:48 ` Otavio Salvador
2018-11-20 15:52 ` Alexey Brodkin
2018-11-20 15:55 ` Marek Vasut
2018-11-20 16:03 ` Otavio Salvador
2018-11-20 15:52 ` Tom Rini
2018-11-20 17:41 ` richard.purdie
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=20181119190835.GO11247@bill-the-cat \
--to=trini@konsulko.com \
--cc=alexey.brodkin@synopsys.com \
--cc=linux-snps-arc@lists.infradead.org \
--cc=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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