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] Right board to use -- buildroot begniers
Date: Tue, 8 Sep 2015 12:01:22 +0200	[thread overview]
Message-ID: <20150908120122.7662cb86@free-electrons.com> (raw)
In-Reply-To: <55EE8B90.9060708@mind.be>

Arnout,

On Tue, 8 Sep 2015 09:17:36 +0200, Arnout Vandecappelle wrote:

> > http://www.at91.com/linux4sam/bin/view/Linux4SAM/BuildRoot
> 
>  Well, the linux4sam fork is relatively old. In addition, there are some changes
> in it that are incorrect. So I'd stick to upstream buildroot :-)

My colleague Alexandre Belloni has recently updated or added numerous
Atmel defconfigs, and Atmel's plan is to deprecate their Buildroot fork
and to just tell people to use the upstream version (at least that's
what I understood).

Alex?

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

  parent reply	other threads:[~2015-09-08 10:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 12:36 [Buildroot] Right board to use -- buildroot begniers Dinesh Guleria
2015-09-07 19:38 ` Arnout Vandecappelle
2015-09-08  2:13   ` Dinesh Guleria
2015-09-08  7:17     ` Arnout Vandecappelle
2015-09-08  8:56       ` Dinesh Guleria
2015-09-08 10:00         ` Thomas Petazzoni
2015-09-08 16:16         ` Luca Ceresoli
2015-09-08 18:03           ` Dinesh Guleria
2015-09-12 11:11             ` Dinesh Guleria
2015-09-13 11:51               ` Dinesh Guleria
2015-09-08 10:01       ` Thomas Petazzoni [this message]
2015-09-08 11:28         ` Alexandre Belloni
2015-09-08 12:34           ` Dinesh Guleria
2015-09-08 13:26             ` Arnout Vandecappelle
2015-09-08 13:26             ` Thomas Petazzoni

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=20150908120122.7662cb86@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