Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] BSP patch
Date: Tue, 10 Apr 2007 14:18:38 +0200	[thread overview]
Message-ID: <20070410121838.GA16751@aon.at> (raw)
In-Reply-To: <017101c771ed$52dbe8c0$01c4af0a@Glamdring>

On Thu, Mar 29, 2007 at 12:30:43PM +0200, Ulf Samuelsson wrote:
>[snip]
>
>>>The BSP patch is really there to allow two different configurations
>>>to be built within the same buildroot directory so they can share:
>>>
>>>* toolchain
>>>* root file system build directory.
>>>but have different configurations for linux kernel and busybox
>>>and eventually you may want to have different content of the root file
>>>system.
>>>
>>>The solution is to create a new directory structure
>>>target_build_<arch>/<board> where everything is built.
>>>The patch allows pre/postfixes to this directory name.
>>>
>>>The BSP patch also put some structure on where the result ends up.
>>>Today everything is stored in the top directory, but if you
>>>want to build multiple boards, then you are going to get a lot of clutter.
>>
>>We need to better differentiate between arch and cpu (generally, not in
>>your board support patch).
>>
>>Applying your patch now locally. Let's see..
>>
>
>Any progress?

[I've just replied to you to a privately sent message, fwiw]

random remarks:
avr32_binutils/toolchain_binutils_binutils.mk.patch
There is already a BR2_ATMEL_MIRROR in the toplevel Config.in, use that
instead.


avr32_binutils/toolchain_binutils_Config.in.patch
I won't comment on you using a deprecated version of binutils (current
release is 2.17).
Please put the !avr32 next to !nios, i.e. before the DEPRECATED.


avr32_kernel_headers/toolchain_kernel-headers_Config.in.patch
I won't comment on you using an old kernel.
Please put the !avr32 before the DEPRECATED


avr32_gcc/toolchain_gcc_Config.in.patch
Please put the !avr32 before the DEPRECATED


avr32_gcc/toolchain_gcc_4.0.2_gcc-4.0.2-atmel.0.99.2.patch.patch
4.0.2 is deprecated. The current stable release is 4.1.2, 4.0.4 was the
last release of 4.0 so far.
There are lots of changes due to RCS IDs in this patch, please drop those
parts.

  reply	other threads:[~2007-04-10 12:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 22:24 [Buildroot] BSP patch Ulf Samuelsson
2007-03-21 22:43 ` Bernhard Fischer
2007-03-21 23:13   ` Ulf Samuelsson
2007-03-22 13:26     ` Bernhard Fischer
2007-03-22 13:53       ` Ulf Samuelsson
2007-03-22 16:40         ` Erik Andersen
2007-03-22 17:24           ` Ulf Samuelsson
2007-04-30 13:37           ` Ulf Samuelsson
2007-03-29 10:30       ` Ulf Samuelsson
2007-04-10 12:18         ` Bernhard Fischer [this message]
2007-04-10 13:22           ` Ulf Samuelsson
2007-04-12 11:02             ` Haavard Skinnemoen
2007-03-21 23:16   ` Ulf Samuelsson
2007-03-22 16:30     ` Erik Andersen
  -- strict thread matches above, loose matches on Subject: below --
2007-04-16 13:57 Ulf Samuelsson
2007-02-16  0:25 [Buildroot] difference between this list and gmane? Daniel Ng
2007-02-16  9:36 ` Bernhard Fischer
2007-02-16 10:18   ` [Buildroot] BSP patch Ulf Samuelsson
2007-01-25 22:44 [Buildroot] (no subject) Ulf Samuelsson
2007-01-28 22:18 ` Bernhard Fischer
2007-01-29  0:26   ` [Buildroot] BSP patch Ulf Samuelsson

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=20070410121838.GA16751@aon.at \
    --to=rep.dot.nop@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox