Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Atmel specific handling in buildroot
Date: Fri, 30 Jan 2009 20:33:07 +0100	[thread overview]
Message-ID: <873af0mvws.fsf@macbook.be.48ers.dk> (raw)

Hi,

Why is it again we have special handling of Atmel targets?

git grep -B2 'default.*if BR2_TARGET_ATMEL'        ~/source/buildroot
target/Config.in-choice
target/Config.in-       prompt "Kernel type"
target/Config.in:       default BR2_KERNEL_LINUX_ADVANCED if BR2_TARGET_ATMEL
target/device/Config.in.linux.patches-  depends on !BR2_KERNEL_PREPATCHED
target/device/Config.in.linux.patches-  default y if BR2_avr32
target/device/Config.in.linux.patches:  default y if BR2_TARGET_ATMEL && BR2_arm
--
target/linux/Config.in.advanced-config BR2_LINUX_COPYTO_TFTPBOOT
target/linux/Config.in.advanced-        bool "Copy kernel to /tftpboot"
target/linux/Config.in.advanced:        default y if BR2_TARGET_ATMEL
--
target/linux/Config.in.advanced-config BR2_LINUX_COPY_CONFIGURATION
target/linux/Config.in.advanced-        bool "Copy buildroot configuration to Li
target/linux/Config.in.advanced:        default y if BR2_TARGET_ATMEL

Do we really need that? It would imho be a lot more sensible if BR
behaved the same way for all archs.

-- 
Bye, Peter Korsgaard

             reply	other threads:[~2009-01-30 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 19:33 Peter Korsgaard [this message]
2009-02-01 15:03 ` [Buildroot] Atmel specific handling in buildroot 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

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=873af0mvws.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