Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit:trunk/buildroot/target/device/Atmel/u-boot
Date: Mon, 30 Jul 2007 16:54:59 +0200	[thread overview]
Message-ID: <026701c7d2c2$c9020670$dcc4af0a@atmel.com> (raw)
In-Reply-To: 20070730101704.GI23273@aon.at

----- Original Message ----- 
From: "Bernhard Fischer" <rep.dot.nop@gmail.com>
To: <buildroot@uclibc.org>
Cc: <ulf@atmel.com>
Sent: Monday, July 30, 2007 12:17 PM
Subject: Re: [Buildroot] svn commit:trunk/buildroot/target/device/Atmel/u-boot


> On Sun, Jul 29, 2007 at 12:05:16AM -0700, ulf at uclibc.org wrote:
>>Author: ulf
>>Date: 2007-07-29 00:05:13 -0700 (Sun, 29 Jul 2007)
>>New Revision: 19312
>>
>>Log:
>>Reintroduce ATMEL_MIRROR in u-boot
>>
>>Modified:
>>   trunk/buildroot/target/device/Atmel/u-boot/u-boot.mk
>>
>>
>>Changeset:
>>Modified: trunk/buildroot/target/device/Atmel/u-boot/u-boot.mk
>>===================================================================
>>--- trunk/buildroot/target/device/Atmel/u-boot/u-boot.mk 2007-07-29 06:51:35 UTC (rev 19311)
>>+++ trunk/buildroot/target/device/Atmel/u-boot/u-boot.mk 2007-07-29 07:05:13 UTC (rev 19312)
>>@@ -8,6 +8,8 @@
>> #
>> #############################################################
>> UBOOT_VERSION:=1.2.0-atmel
>>+ATMEL_MIRROR:=$(strip  $(subst ",, $(BR2_ATMEL_MIRROR)))
>>+#"))
> 
> This is redundant.
> What about doing this once, cleanly?
> 
> target/device/Atmel/Makefile.in would be the obvious place where i'd put
> this once and for all..
>

The AVR32 patches for the toolchain is 6-8 MB and I would like to avoid that.
I am working on a patch that will allow you to download prepatched source
for the AVR32 (binutils, gcc, uclibc and gdb).
Therefore, ATMEL_MIRROR needs to be set before the toolchain is built.

The first version had ATMEL_MIRROR set in each of the files.
The I moved to a common definition, which has to be before that,
so I put it in "package/Makefile.in", and this was reverted.
Since it needs to be available before the toolchain is built, 
Stephen suggested to have it in each toolchain Makefile, resulting in the
"VENDOR" patches, which I agree should be less vendor specific.

I spend some time thinking about  this today (while waiting on the tees of the local golfcourse)
and I think that the best idea is to have another option in the 
"Toolchain type" menu so you can select an externally prepatched toolchain.
(X) Buildroot toolchain
(  )  Prepatched toolchain source
(  )  External Toolchain

If you select "Prepatched toolchain source", then you get to select vendor as a choice.
Otherwise it is hidden.
Then the 
VENDOR_SITE
VENDOR_SUFFIX
VENDOR_RELEASE
strings are set.

VENDOR_SITE could be set to $(BR2_ATMEL_MIRROR) if an Atmel 
prepatched toolchain is selected.

If it is implemented this way, then ATMEL_MIRROR could be set
once in the "target/device/Atmel/Makefile.in"

Best Regards
Ulf Samuelsson

  reply	other threads:[~2007-07-30 14:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29  7:05 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/u-boot ulf at uclibc.org
2007-07-30 10:17 ` Bernhard Fischer
2007-07-30 14:54   ` Ulf Samuelsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-10 21:03 ulf at uclibc.org
2008-04-11 20:55 ` Jean-Christian de Rivaz
2008-04-11 21:32   ` Peter Korsgaard
2008-04-12  7:42     ` Jean-Christian de Rivaz
2008-04-12  8:13       ` Peter Korsgaard
2008-03-02 10:25 thomasez at uclibc.org
2007-10-21 20:09 ulf at uclibc.org
2007-09-04 16:20 ulf at uclibc.org
2007-09-01 10:54 aldot at uclibc.org
2007-08-28 21:07 ulf at uclibc.org
2007-07-20 14:39 sjhill at uclibc.org
2007-07-20 11:13 ulf at uclibc.org
2007-07-20  7:54 ulf at uclibc.org

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='026701c7d2c2$c9020670$dcc4af0a@atmel.com' \
    --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