From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Atmel specific handling in buildroot
Date: Sun, 01 Feb 2009 19:57:27 +0100 [thread overview]
Message-ID: <87vdrugf3c.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1233509597.5742.35.camel@elrond.atmel.com> (Ulf Samuelsson's message of "Sun\, 01 Feb 2009 18\:33\:17 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Hi,
Ulf> I dont think you will build correctly unless you use the
Ulf> advanced kernel setting for the AVR32 and AT91.
Huh, why wouldn't BR2_KERNEL_none work for those targets?
Ulf> Copying the build configuration to the root file system
Ulf> is in line with the open source model, since
Ulf> it helps people to reproduce whatever is on the board
Ulf> if they buy the product.
Not only that, That info is required by the license.
Ulf> If you want to debug something, then it is good to
Ulf> know how it was configured.
Ulf> If someone calls in with a board without this, then it is
Ulf> too late to do anything about it.
Ulf> Obviously, since I put it there, I want to have it ON
Ulf> for all my customers.
Fine, that's why we have the configuration in the first place I
guess - But the question isn't about what you or your customers want,
it's about what the default should be in BR.
It makes sense to default these to off like for everything else, so
I'll remove the atmel special case.
Ulf> As for the copyto, this is a convenience, and people
Ulf> can configure whatever they want.
Ulf> I find that it saves time to have this on.
Again, feel free to use it, but it shouldn't be default (E.G. it
breaks the build when you don't have a /tftpboot and/or it isn't
writable.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-02-01 18:57 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
2009-02-01 18:57 ` Peter Korsgaard [this message]
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=87vdrugf3c.fsf@macbook.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