All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Atmel specific handling in buildroot
Date: Sun, 01 Feb 2009 16:36:34 +0100	[thread overview]
Message-ID: <1233502594.5742.24.camel@elrond.atmel.com> (raw)
In-Reply-To: <874ozei4hg.fsf@macbook.be.48ers.dk>

s?n 2009-02-01 klockan 16:03 +0100 skrev Peter Korsgaard:
> >>>>> "Peter" == Peter Korsgaard <jacmet@uclibc.org> writes:
> 
>  Peter> Hi,
>  Peter> Why is it again we have special handling of Atmel targets?
> 
> ..
>  Peter> target/linux/Config.in.advanced:        default y if BR2_TARGET_ATMEL
> 
>  Peter> Do we really need that? It would imho be a lot more sensible if BR
>  Peter> behaved the same way for all archs.

There are several things here

1) If there is an architecture patch available for an architecture,
   then it should have default yes.
   I can't think of a situation where you prefer not to apply
   the architecture patch for the AT91 or AVR32.
   The only reason is that you are building a kernel for where
   there is no valid patch.
   If there is no architecture patch, then obviously 
   it should be default no.

2) I think that we should reduce the choice to 
   only have no kernel or the advanced configuration.

3) For copy to, that should be collected to a single copy to

BR
Ulf Samuelsson



> 
> No objections? Good, then I'll remove them.
> 

  reply	other threads:[~2009-02-01 15:36 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 [this message]
2009-02-01 16:13     ` Peter Korsgaard
2009-02-01 17:33       ` Ulf Samuelsson
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=1233502594.5742.24.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.