From: Pieter Smith <pieter@boesman.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [v2, 0/4] Supporting building a second Barebox config
Date: Wed, 20 Jan 2016 23:47:42 +0100 [thread overview]
Message-ID: <20160120224742.GA3128@smipidev> (raw)
In-Reply-To: <CAGm1_kuK9-vd6-293KqYSyzqLT9m_+yLXnT_ach85mRzmKefhg@mail.gmail.com>
Hi Yegor,
On Tue, Jan 19, 2016 at 11:11:44AM +0100, Yegor Yefremov wrote:
> Hi Pieter,
>
> On Wed, Nov 4, 2015 at 10:20 PM, Pieter Smith <pieter@boesman.nl> wrote:
> > This patch-set in 4 parts adds support for building barebox with up to 2
> > configurations. It can be used to build the barebox x-loader or MLO (also
> > called Secondary Program Loader) in addition to the standard barebox build
> > (Tertiary Program Loader). This implements the design proposed in
> > http://elinux.org/Buildroot#Todo_list:
> > 1. Have boot/barebox/ containing the common stuff.
> > 2. Add two separate packages boot/barebox-1/ and boot/barebox-2/.
> > 3. There is only one version selection, but each package allows to
> > define the configuration to be used.
> > 4. Design is a little bit like package/gcc, where we have multiple gcc builds,
> > but share a lot of common definitions between the packages.
> >
> > To demonstrate that it works as advertized, the last patch adds a defconfig for
> > the beaglebone black that makes use of the added functionality.
> >
> > Pieter Smith (4):
> > barebox: prepare for secondary config build
> > barebox: adds option to build secondary config
> > barebox: user selection of build output images
> > beaglebone: adds barebox bootloader defconfig
> >
> > boot/barebox/Config.in | 155 +++++++++++++++++++++++++++++-----
> > boot/barebox/barebox-1/barebox-1.hash | 1 +
> > boot/barebox/barebox-1/barebox-1.mk | 89 +++++++++++++++++++
> > boot/barebox/barebox-2/barebox-2.hash | 1 +
> > boot/barebox/barebox-2/barebox-2.mk | 51 +++++++++++
> > boot/barebox/barebox.mk | 60 +------------
> > configs/beaglebone_barebox_defconfig | 39 +++++++++
> > 7 files changed, 317 insertions(+), 79 deletions(-)
> > create mode 120000 boot/barebox/barebox-1/barebox-1.hash
> > create mode 100644 boot/barebox/barebox-1/barebox-1.mk
> > create mode 120000 boot/barebox/barebox-2/barebox-2.hash
> > create mode 100644 boot/barebox/barebox-2/barebox-2.mk
> > create mode 100644 configs/beaglebone_barebox_defconfig
>
> Thanks for the patches. Just wanted to review/test them. They don't
> apply cleanly.
> Could you please rebase your patches on top of the master branch?
>
> Thanks.
>
> Yegor
As requested, I rebased the patches onto the latest master and reposted bumping
to v3. I look forward to your feedback.
Regards,
Pieter
prev parent reply other threads:[~2016-01-20 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 21:20 [Buildroot] [v2, 0/4] Supporting building a second Barebox config Pieter Smith
2015-11-04 21:20 ` [Buildroot] [v2, 1/4] barebox: prepare for secondary config build Pieter Smith
2015-11-04 21:20 ` [Buildroot] [v2, 2/4] barebox: adds option to build secondary config Pieter Smith
2015-11-04 21:20 ` [Buildroot] [v2, 3/4] barebox: user selection of build output images Pieter Smith
2015-11-04 21:20 ` [Buildroot] [v2, 4/4] beaglebone: adds barebox bootloader defconfig Pieter Smith
2016-01-19 10:11 ` [Buildroot] [v2, 0/4] Supporting building a second Barebox config Yegor Yefremov
2016-01-20 22:47 ` Pieter Smith [this message]
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=20160120224742.GA3128@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