From: Pieter Smith <pieter@boesman.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 0/7] Support building a second Barebox config (incl. BBB)
Date: Sat, 23 Apr 2016 18:18:44 +0200 [thread overview]
Message-ID: <20160423161844.GA9825@smipidev> (raw)
In-Reply-To: <20160423165013.10739b58@free-electrons.com>
Hi Thomas,
On Sat, Apr 23, 2016 at 04:50:13PM +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Sat, 23 Apr 2016 14:35:22 +0000, Pieter Smith wrote:
>
> > As I already voiced, I would like to have the defconfig in as a
> > usage example.
>
> 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 ;-)
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?
> 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... ;-)
> And IMO, having a defconfig whose only difference from the
> beaglebone_defconfig is to use Barebox instead of U-Boot is not a
> useful defconfig.
I can't find fault with your logic. I am all too aware of how painful the
maintenance burden can become if you don't say no often enough.
> 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?
> > I also find the BBB with barebox much easier to play with. It
> > boots faster and is much easier to script.
>
> That's very subjective, and the default/defacto standard on BeagleBone
> remains U-Boot (no matter how much I would prefer Barebox to become
> more popular).
Oh, if I could change the world... ;-)
Regards,
Pieter
[snip]
next prev parent reply other threads:[~2016-04-23 16:18 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 22:35 [Buildroot] [PATCH v4 0/7] Support building a second Barebox config (incl. BBB) Pieter Smith
2016-03-20 22:35 ` [Buildroot] [PATCH v4 1/7] barebox: support multi-image-build image selection Pieter Smith
2016-03-31 5:44 ` Yegor Yefremov
2016-04-06 20:28 ` Pieter Smith
2016-04-02 15:31 ` Thomas Petazzoni
2016-04-04 22:08 ` Arnout Vandecappelle
2016-04-04 22:16 ` Arnout Vandecappelle
2016-03-20 22:35 ` [Buildroot] [PATCH v4 2/7] barebox: friendly error on missing built image Pieter Smith
2016-03-31 6:01 ` Yegor Yefremov
2016-03-20 22:35 ` [Buildroot] [PATCH v4 3/7] barebox: support custom barebox output image name Pieter Smith
2016-03-31 6:03 ` Yegor Yefremov
2016-04-04 22:31 ` Arnout Vandecappelle
2016-04-04 23:20 ` Arnout Vandecappelle
2016-04-06 14:53 ` Thomas Petazzoni
2016-04-06 20:14 ` Pieter Smith
2016-04-06 23:06 ` Arnout Vandecappelle
2016-04-08 7:51 ` Pieter Smith
2016-03-20 22:35 ` [Buildroot] [PATCH v4 4/7] barebox: introduce barebox-package function Pieter Smith
2016-03-31 6:12 ` Yegor Yefremov
2016-04-04 22:59 ` Arnout Vandecappelle
2016-04-04 23:23 ` Arnout Vandecappelle
2016-04-06 20:26 ` Pieter Smith
2016-03-20 22:35 ` [Buildroot] [PATCH v4 5/7] barebox: extract package name argument Pieter Smith
2016-03-31 6:16 ` Yegor Yefremov
2016-04-04 23:01 ` Arnout Vandecappelle
2016-03-20 22:35 ` [Buildroot] [PATCH v4 6/7] barebox: support 2nd config build Pieter Smith
2016-03-31 6:17 ` Yegor Yefremov
2016-04-04 23:25 ` Arnout Vandecappelle
2016-04-24 7:53 ` Pieter Smith
2016-03-20 22:35 ` [Buildroot] [PATCH v4 7/7] beaglebone: adds barebox bootloader defconfig Pieter Smith
2016-03-31 6:21 ` Yegor Yefremov
2016-04-04 23:37 ` Arnout Vandecappelle
2016-04-19 20:26 ` Pieter Smith
2016-04-19 22:13 ` Arnout Vandecappelle
2016-04-23 11:39 ` Pieter Smith
2016-03-21 11:38 ` [Buildroot] [PATCH v4 0/7] Support building a second Barebox config (incl. BBB) Yegor Yefremov
2016-03-21 11:56 ` Pieter Smith
2016-04-19 19:24 ` Thomas Petazzoni
2016-04-19 20:17 ` Pieter Smith
2016-04-20 14:42 ` Yegor Yefremov
2016-04-20 16:42 ` Pieter Smith
2016-04-21 10:55 ` Yegor Yefremov
2016-04-21 11:29 ` Thomas Petazzoni
2016-04-23 13:01 ` Pieter Smith
2016-04-23 13:11 ` Thomas Petazzoni
2016-04-23 14:35 ` Pieter Smith
2016-04-23 14:50 ` Thomas Petazzoni
2016-04-23 16:18 ` Pieter Smith [this message]
2016-04-23 19:26 ` Thomas Petazzoni
2016-04-24 8:04 ` Pieter Smith
2016-04-24 8:16 ` Thomas Petazzoni
2016-04-24 8:32 ` Pieter Smith
2016-04-24 8:47 ` Thomas Petazzoni
2016-04-24 8:50 ` Pieter Smith
2016-04-24 8:47 ` Pieter Smith
2016-04-24 19:18 ` Peter Korsgaard
2016-04-24 21:26 ` Pieter Smith
2016-04-23 13:05 ` Pieter Smith
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=20160423161844.GA9825@smipidev \
--to=pieter@boesman.nl \
--cc=buildroot@busybox.net \
/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