[OE-core] [PATCH] u-boot-fw-utils: Allow replacement of fw_env.config

[Tom Rini]

On Wed, Jun 21, 2017 at 03:01:36PM -0300, Otavio Salvador wrote:
> On Wed, Jun 21, 2017 at 1:52 PM, Tom Rini <trini at konsulko.com> wrote:
> > On Wed, Jun 21, 2017 at 11:50:23AM -0400, Denys Dmytriyenko wrote:
> >> What I'm arguing against here is some partial solution - modifying the global
> >> recipe in oe-core, but still require .bbappend to provide a file. It's should
> >> either be "do everything in .bbappend, like we all do now" or "do everything
> >> in main oe-core recipe and let machine.conf define it".
> >
> > OK, we should do it globally with a ??= of the in-tree example only?  Or
> > just let u-boot-fw-utils fail to build?
> 
> Maybe the best is to allow for boards to have its fw_env.config inside
> U-Boot so people can provide a 'good' base for users. Doing so, we can
> teach the recipe to install it?

No, I don't like that.  One could generate probably-correct config for
NAND/NOR.  But UBI and FAT (and EXT4) start to become a per-distro
thing.  This is even somewhat true of MMC where it's more likely that
you'll know what maps out to /dev/mmcblk0 vs /dev/mmcblk1, and upstream
U-Boot won't know what kernel people are going to boot and then have
give a device name.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170621/01453e94/attachment-0002.sig>