From: trini@konsulko.com (Tom Rini)
To: linux-snps-arc@lists.infradead.org
Subject: [OE-core] [PATCH v3] u-boot: Add mkenvimage tool
Date: Tue, 20 Nov 2018 10:52:17 -0500 [thread overview]
Message-ID: <20181120155217.GA11247@bill-the-cat> (raw)
In-Reply-To: <CAP9ODKqKDfJ11FLoXFwRZ3ttw4v3NODWEQdB7RkCAzHq7DWPiw@mail.gmail.com>
On Tue, Nov 20, 2018@01:48:40PM -0200, Otavio Salvador wrote:
> On Tue, Nov 20, 2018@1:40 PM Burton, Ross <ross.burton@intel.com> wrote:
> >
> > (hit sent too early)
> >
> > Of course how big are these tools, and is it really useful splitting
> > them up? If we're talking a 10k binary, is putting them in separate
> > packages worth the complication?
>
> I think it makes sense to split; we are building an embedded system
> build system and granular installation is a must have. Using PN to
> install all tools is a win win combination.
Agreed. The common use cases won't need all of the possible tools so
lets not grow sizes we don't need to grow.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-snps-arc/attachments/20181120/5e8f3cba/attachment-0001.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Tom Rini <trini@konsulko.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Marek Vasut <marex@denx.de>,
Otavio Salvador <otavio@ossystems.com.br>,
Alexey Brodkin <alexey.brodkin@synopsys.com>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
linux-snps-arc@lists.infradead.org
Subject: Re: [PATCH v3] u-boot: Add mkenvimage tool
Date: Tue, 20 Nov 2018 10:52:17 -0500 [thread overview]
Message-ID: <20181120155217.GA11247@bill-the-cat> (raw)
In-Reply-To: <CAP9ODKqKDfJ11FLoXFwRZ3ttw4v3NODWEQdB7RkCAzHq7DWPiw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
On Tue, Nov 20, 2018 at 01:48:40PM -0200, Otavio Salvador wrote:
> On Tue, Nov 20, 2018 at 1:40 PM Burton, Ross <ross.burton@intel.com> wrote:
> >
> > (hit sent too early)
> >
> > Of course how big are these tools, and is it really useful splitting
> > them up? If we're talking a 10k binary, is putting them in separate
> > packages worth the complication?
>
> I think it makes sense to split; we are building an embedded system
> build system and granular installation is a must have. Using PN to
> install all tools is a win win combination.
Agreed. The common use cases won't need all of the possible tools so
lets not grow sizes we don't need to grow.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2018-11-20 15:52 UTC|newest]
Thread overview: 28+ 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 10:04 ` Alexey Brodkin
2018-11-19 12:51 ` Marek Vasut
2018-11-19 12:51 ` Marek Vasut
2018-11-19 19:08 ` [OE-core] " Tom Rini
2018-11-19 19:08 ` Tom Rini
2018-11-19 19:22 ` [OE-core] " Otavio Salvador
2018-11-19 19:22 ` Otavio Salvador
2018-11-19 19:47 ` [OE-core] " Alexey Brodkin
2018-11-19 19:47 ` Alexey Brodkin
2018-11-20 14:29 ` [OE-core] " Peter Kjellerstedt
2018-11-20 14:29 ` Peter Kjellerstedt
2018-11-20 15:39 ` [OE-core] " Burton, Ross
2018-11-20 15:39 ` Burton, Ross
2018-11-20 15:40 ` [OE-core] " Burton, Ross
2018-11-20 15:40 ` Burton, Ross
2018-11-20 15:48 ` [OE-core] " Otavio Salvador
2018-11-20 15:48 ` Otavio Salvador
2018-11-20 15:52 ` [OE-core] " Alexey Brodkin
2018-11-20 15:52 ` Alexey Brodkin
2018-11-20 15:55 ` [OE-core] " Marek Vasut
2018-11-20 15:55 ` Marek Vasut
2018-11-20 16:03 ` [OE-core] " Otavio Salvador
2018-11-20 16:03 ` Otavio Salvador
2018-11-20 15:52 ` Tom Rini [this message]
2018-11-20 15:52 ` Tom Rini
2018-11-20 17:41 ` richard.purdie
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=20181120155217.GA11247@bill-the-cat \
--to=trini@konsulko.com \
--cc=linux-snps-arc@lists.infradead.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 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.