From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Atmel specific handling in buildroot
Date: Sun, 01 Feb 2009 18:33:17 +0100 [thread overview]
Message-ID: <1233509597.5742.35.camel@elrond.atmel.com> (raw)
In-Reply-To: <87zlh6gmod.fsf@macbook.be.48ers.dk>
s?n 2009-02-01 klockan 17:13 +0100 skrev Peter Korsgaard:
> >>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
>
> Ulf> There are several things here
>
> Ulf> 1) If there is an architecture patch available for an architecture,
> Ulf> then it should have default yes.
> Ulf> I can't think of a situation where you prefer not to apply
> Ulf> the architecture patch for the AT91 or AVR32.
> Ulf> The only reason is that you are building a kernel for where
> Ulf> there is no valid patch.
> Ulf> If there is no architecture patch, then obviously
> Ulf> it should be default no.
>
> Ok, but that's only one of the settings, so you're fine with me fixing
> the COPYTO / kernel type thingies?
I dont think you will build correctly unless you use the advanced kernel
setting for the AVR32 and AT91.
Copying the build configuration to the root file system
is in line with the open source model, since
it helps people to reproduce whatever is on the board
if they buy the product.
If you want to debug something, then it is good to
know how it was configured.
If someone calls in with a board without this, then it is
too late to do anything about it.
Obviously, since I put it there, I want to have it ON
for all my customers.
As for the copyto, this is a convenience, and people
can configure whatever they want.
I find that it saves time to have this on.
BR
Ulf Samuelsson
next prev parent reply other threads:[~2009-02-01 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 19:33 [Buildroot] Atmel specific handling in buildroot Peter Korsgaard
2009-02-01 15:03 ` Peter Korsgaard
2009-02-01 15:36 ` Ulf Samuelsson
2009-02-01 16:13 ` Peter Korsgaard
2009-02-01 17:33 ` Ulf Samuelsson [this message]
2009-02-01 18:57 ` Peter Korsgaard
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=1233509597.5742.35.camel@elrond.atmel.com \
--to=ulf.samuelsson@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.