From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: at91rm9200df at91sam9260dfc at91sam9261e etc...
Date: Sat, 31 Jan 2009 23:03:10 +0100 [thread overview]
Message-ID: <87k58bjfq9.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090131214405.4A8147621A@busybox.osuosl.org> (ulf@uclibc.org's message of "Sat\, 31 Jan 2009 21\:44\:05 +0000 \(UTC\)")
>>>>> "ulf" == ulf <ulf@uclibc.org> writes:
ulf> Author: ulf
ulf> Date: 2009-01-31 21:44:04 +0000 (Sat, 31 Jan 2009)
ulf> New Revision: 25199
ulf> Log:
ulf> Add AT91 defconfigs for binary toolchains
ulf> Added:
ulf> trunk/buildroot/target/device/Atmel/at91rm9200df/at91rm9200df_ext_bare_defconfig
ulf> trunk/buildroot/target/device/Atmel/at91rm9200df/at91rm9200df_ext_defconfig
ulf> trunk/buildroot/target/device/Atmel/at91sam9261ek/at91sam9261ek_ext_bare_defconfig
ulf> trunk/buildroot/target/device/Atmel/at91sam9261ek/at91sam9261ek_ext_defconfig
ulf> trunk/buildroot/target/device/Atmel/at91sam9263ek/at91sam9263ek_ext_bare_defconfig
ulf> trunk/buildroot/target/device/Atmel/at91sam9263ek/at91sam9263ek_ext_defconfig
ulf> trunk/buildroot/target/device/Atmel/at91sam9g20dfc/at91sam9g20dfc_ext_bare_defconfig
ulf> trunk/buildroot/target/device/Atmel/at91sam9g20dfc/at91sam9g20dfc_ext_defconfig
I'm really not convinced we need (to keep updated) all those
defconfigs.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-31 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 21:44 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel: at91rm9200df at91sam9260dfc at91sam9261e etc ulf at uclibc.org
2009-01-31 22:03 ` Peter Korsgaard [this message]
2009-01-31 22:29 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2008-03-30 20:42 ulf at uclibc.org
2007-08-11 23:09 ulf at uclibc.org
2007-07-29 7:34 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=87k58bjfq9.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 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.