[Buildroot] [PATCH v4 0/7] Support building a second Barebox config (incl. BBB)

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Hello,

On Sat, 23 Apr 2016 18:18:44 +0200, Pieter Smith wrote:

> > Well, what you want and what the Buildroot maintainer/core developers
> > want may be different :-)
> 
> Yup... If all the world was of one mind, it surely would be a boring place ;-)

Indeed :)

> I do not want to try to force the beaglebone_barebox_defconfig. Everybody knows
> that it doesn't work that way. Is there no value in having SOME FORM of
> defconfig to illustrate feature use in buildroot?

There is a value, but not as a defconfig in configs/ IMO.
Unfortunately, the place/infrastructure where it would have a value
doesn't really exist today.

> > My opinion is that there is no point is having gazillions of different
> > defconfigs for the same board. Your focus is on Barebox, but then the
> > next developer will want a defconfig for BeagleBone+Qt5, the next one
> > for BeagleBone+Wayland, the next one for BeagleBone+Kodi, the next one
> > for BeagleBone as a toaster controller, etc, etc. As you can see, it's
> > going to be an endless list of unmaintainable defconfigs, so we have to
> > cut the line somewhere.
> 
> What? No beaglebone_epilator_defconfig? Pity... ;-)

beaglebone_toothbrush_defconfig :-)

> > It would however be useful in a "testing" framework so that we can
> > validate automatically that the dual Barebox functionality continues to
> > work over time.
> 
> Agreed. Where can I stall my shiny BBB barebox "regression test" roadster then?

My grand plan is to promote something like
https://github.com/tpetazzoni/buildroot-runtime-test in order to
collect test cases (both build-time tests and runtime tests).

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com