All of 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:atngw100 atngw100-base atngw100-expanded etc...
Date: Tue, 6 May 2008 13:03:54 +0200	[thread overview]
Message-ID: <008e01c8af69$830eef00$5e8d910a@atmel.com> (raw)
In-Reply-To: 46a136670805051855v20cfee30o267907b605f6bc9a@mail.gmail.com

> The ftp site seems to be out-of-date. The latest avr32 patches for gcc are
> for version 4.2.2 with atmel patch 1.0.8. I'm not sure about the others
> though. Also, they don't seem to be patched with the other uClibc patches as
> well, and there is no facility in buildroot to patch the pre-patched files
> either, as gcc 4.2.2 doesn't even have a toolchain directory. I've got
> pre-patched sources here: ftp://64.31.81.93 that includes avr32-atmel.1.0.8
> and all of the other uClibc patches as well. If you want to move them to the
> at91 site that would be great. 

I will move this later this week.

> A couple of us AVR32 users have been
> discussing the patch.avr32 scheme, is this out of the question?

What is the benefit?
You can add patches to the AVR32 prepatched toolchain at "target/device/Atmel/toolchain"
Just need to add the correct directories.

The drawback of having patches inside the svn is that everyone not
using AVR32 will have to suffer the additional download.

> Regards,
> John Voltz



Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

  reply	other threads:[~2008-05-06 11:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06  1:38 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: atngw100 atngw100-base atngw100-expanded etc ulf at uclibc.org
2008-05-06  1:55 ` John Voltz
2008-05-06 11:03   ` Ulf Samuelsson [this message]
2008-05-06 17:19     ` [Buildroot] svn commit: trunk/buildroot/target/device/Atmel:atngw100 " Thiago A. Corrêa
2008-05-07  9:01       ` [Buildroot] svn commit:trunk/buildroot/target/device/Atmel:atngw100 atngw100-baseatngw100-expanded etc Ulf Samuelsson
2008-05-07 12:18   ` [Buildroot] svn commit: trunk/buildroot/target/device/Atmel:atngw100 atngw100-base atngw100-expanded etc 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='008e01c8af69$830eef00$5e8d910a@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 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.