Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] defconfigs: add sama5d3 support
Date: Tue, 04 Feb 2014 10:06:13 +0100	[thread overview]
Message-ID: <87y51rl01m.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1391093726-7569-1-git-send-email-ludovic.desroches@atmel.com> (ludovic desroches's message of "Thu, 30 Jan 2014 15:55:26 +0100")

>>>>>   <ludovic.desroches@atmel.com> writes:

 > From: Ludovic Desroches <ludovic.desroches@atmel.com>
 > Defconfig file for boards based on sama5d3x devices.

 > Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
 > ---

 > Hi,

 > This is a basic defconf file for sama5d3 devices. at91boostrap, u-boot, linux
 > stuff will come later.

Thanks, but we prefer our defconfigs to just be the minimal needed to
configure buildroot for the hardware (arch/variant, bootloader, kernel)
- E.G. something like configs/nitrogen6x_defconfig

Care to send such a minimal defconfig with comments instead?

 >> From the top of my head Alexandre Belloni told me that some flags have to be
 > added for hardware floating point use. It was on a previous version when
 > hard floating has been introduced. Is it still true or does selecting EABIHF is
 > enough?

Selecting EABIHF should afaik be enough.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2014-02-04  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 14:55 [Buildroot] [PATCH] defconfigs: add sama5d3 support ludovic.desroches at atmel.com
2014-02-04  9:06 ` Peter Korsgaard [this message]
2014-02-04 11:26   ` Ludovic Desroches
2014-02-04 12:47     ` Peter Korsgaard
2014-02-04 13:21       ` Ludovic Desroches
2014-02-04 14:24         ` Peter Korsgaard
2014-02-04 16:54           ` Arnout Vandecappelle
2014-02-04 20:33             ` Ludovic Desroches
2014-10-06 15:10 ` 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=87y51rl01m.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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