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] [PATCH 1/4] configs: atmel: unify and update defconfig for Xplained boards
Date: Thu, 24 Mar 2016 09:46:55 +0100	[thread overview]
Message-ID: <20160324094655.007db654@free-electrons.com> (raw)
In-Reply-To: <20160324084344.GD12245@odux.rfo.atmel.com>

Hello,

On Thu, 24 Mar 2016 09:43:44 +0100, Ludovic Desroches wrote:

> On Thu, Mar 24, 2016 at 09:40:06AM +0100, Thomas Petazzoni wrote:
> > Hello,
> > 
> > I'm adding in Cc: Alexandre Belloni, who has worked on Atmel defconfigs
> > in the past.
> 
> He was in Cc.

Gah, my bad. Alex must have chosen in his mailing list preferences to
remove duplicates or something like that, because on the mailing list,
your Cc to Alex was clearly not visible. Hence my comment.

> > > - use bootstrap as first stage bootloader
> > 
> > As opposed to? Did you mean at91bootstrap3 rather than "bootstrap"?
> 
> As opposed to u-boot spl which is less tested than at91bootstrap3.

OK. I think Alex has a somewhat different opinion on the matter, but I
guess that if the vendor recommends to use at91bootstrap3, we should
use this solution in our defconfig.

> > This is not good. linux-4.1-at91 is a branch name, which means that the
> > actual source behind this branch name will change over time, making
> > this defconfig non-reproducible. You must stick to a tag or a commit id.
> 
> In fact it was the plan in order to prevent the need to update these
> defconfig files. If I must stick to a tag then I will use linux4sam
> releases.

We really want our defconfigs to be reproducible in terms of
bootloader/kernel versions. Otherwise, what people will build/test is
not something that the person submitting the defconfig has tested.

Thanks!

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

  reply	other threads:[~2016-03-24  8:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24  8:29 [Buildroot] [PATCH 1/4] configs: atmel: unify and update defconfig for Xplained boards Ludovic Desroches
2016-03-24  8:29 ` [Buildroot] [PATCH 2/4] configs: atmel: add support for sama5d4 xplained boot from sd card Ludovic Desroches
2016-03-24  8:29 ` [Buildroot] [PATCH 3/4] configs: atmel: add sama5d2 xplained support Ludovic Desroches
2016-03-24  8:41   ` Thomas Petazzoni
2016-03-24  8:29 ` [Buildroot] [PATCH 4/4] board/atmel/xplained/readme.txt: update documentation Ludovic Desroches
2016-03-24  8:44   ` Thomas Petazzoni
2016-03-24  9:40     ` Ludovic Desroches
2016-03-24  9:52       ` Thomas Petazzoni
2016-03-24 10:03         ` Ludovic Desroches
2016-03-24  8:40 ` [Buildroot] [PATCH 1/4] configs: atmel: unify and update defconfig for Xplained boards Thomas Petazzoni
2016-03-24  8:43   ` Ludovic Desroches
2016-03-24  8:46     ` Thomas Petazzoni [this message]
2016-03-24  8:54       ` Ludovic Desroches
2016-03-24  9:01         ` Alexandre Belloni

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=20160324094655.007db654@free-electrons.com \
    --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