From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] BSP patch
Date: Thu, 22 Mar 2007 14:53:12 +0100 [thread overview]
Message-ID: <01a101c76c8a$2450a4e0$01c4af0a@Glamdring> (raw)
In-Reply-To: 20070322132609.GA11410@aon.at
>>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..
>
Thank You,
So far the patch does not create anything, only defines locations.
The beef is in the patches that follows
but I plan to submit the AVR32 toolset patches first.
The idea is to avoid keeping the toolset patches
inside the buildroot,and instead download the patches
before they are applied.
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2007-03-22 13:53 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 [this message]
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
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='01a101c76c8a$2450a4e0$01c4af0a@Glamdring' \
--to=ulf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox