Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork oldest patches cleanup #5 (deadline January 19)
Date: Tue, 28 Jan 2014 20:56:32 +0100	[thread overview]
Message-ID: <20140128205632.7b5c3100@skate> (raw)
In-Reply-To: <CAAXf6LVhGnZrVy7bTPjWa+xjbHtKrHU6pFE8aVmAmjbEB_X46w@mail.gmail.com>

Dear Thomas De Schampheleire,

On Mon, 20 Jan 2014 21:58:52 +0100, Thomas De Schampheleire wrote:

> > [RFC,1/2] barebox: Build barebox in separate directory.
> > Marek Belisko <marek.belisko@open-nandra.com>
> > http://patchwork.ozlabs.org/patch/207942
> >
> > [RFC,2/2] barebox: Add possibility to build also barebox xloader (MLO).
> > Marek Belisko <marek.belisko@open-nandra.com>
> > http://patchwork.ozlabs.org/patch/207943
> 
> No feedback. I would tend to reject these two patches, unless someone
> still pops up and wants to adopt these patches. They introduce a
> second build of barebox: one for the standard barebox, and another one
> for the xloader. In fact, the only real difference seems to be that
> both builds use a separate config file.

In fact, there is a real problem that these patches from Marek are
trying to solve. Contrary to U-Boot with which a single build produces
both the first stage bootloader (SPL) and the second stage bootloader
(which is compatible with how Buildroot builds U-Boot), Barebox needs
two completely separate builds in this case. This means that currently,
Buildroot is unable, for some platforms, to generate both the first
stage and the second stage Barebox bootloaders.

Unfortunately, I don't really see a very clean solution to this
problem.

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

  reply	other threads:[~2014-01-28 19:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05 16:01 [Buildroot] Patchwork oldest patches cleanup #5 (deadline January 19) Thomas De Schampheleire
2014-01-05 16:03 ` Thomas De Schampheleire
2014-01-05 16:25   ` Yann E. MORIN
2014-01-05 16:20 ` Yann E. MORIN
2014-01-05 17:17   ` Yann E. MORIN
2014-01-20 20:37     ` Thomas De Schampheleire
2014-01-20 21:20       ` Yann E. MORIN
2014-01-09 20:40   ` Yann E. MORIN
2014-01-20 20:44     ` Thomas De Schampheleire
2014-01-06 13:45 ` Matthew Weber
2014-01-20 20:43   ` Thomas De Schampheleire
2014-01-18 15:35 ` Thomas De Schampheleire
2014-01-20 20:58 ` Thomas De Schampheleire
2014-01-28 19:56   ` Thomas Petazzoni [this message]
2014-02-03  9:43     ` Thomas De Schampheleire
2014-02-04  9:34       ` Thomas De Schampheleire

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=20140128205632.7b5c3100@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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