From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot for avr32
Date: Thu, 29 Nov 2012 11:37:10 +0100 [thread overview]
Message-ID: <20121129113710.63d5676c@skate> (raw)
In-Reply-To: <memo.20121129102031.4232H@postmaster+dexdyne.com.cix.co.uk>
Dear David Collier,
On Thu, 29 Nov 2012 10:20 +0000 (GMT Standard Time), David Collier
wrote:
> Hi - we have a design based on the AVR32.
Aaah great!
> Historically Atmel provided a "special-buildroot-for-AVR32". Trouble is
> their only AVR32 that ran Linux is now end-of-life, and I'm not sure they
> have any interest.
>
> The last version of it I can find is based on a buildroot that is 2 years
> out of date.
>
> So the question is - should I be able to use "standard buildroot" with an
> AVR32 - or was Atmel adding some magic of their own that has not been
> back-ported to the main trunk?
Good to see someone using AVR32. We've been wondering what to do with
our AVR32 support, because not many people have been using it.
Normally, we have a working AVR32 setup, with certainly old versions of
uClibc, binutils and gdb. I was told by AVR32 people that upgrading to
uClibc 0.9.33 should work, but there are a few missing system calls in
the AVR32 upstream kernel. If you are interested, we can look at this
together, as I lack AVR32 hardware to dive into this.
So, I would definitely be interested if you could try out the mainline
Buildroot, and report what the problems are (if any), and we'll see how
to move from here.
Of course, if you are aware of the availability for AVR32 of a more
recent gcc than the 4.2.x we're using and a more recent binutils than
the 2.18 we're using, we're interested as well.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-29 10:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 10:20 [Buildroot] Buildroot for avr32 David Collier
2012-11-29 10:37 ` Thomas Petazzoni [this message]
2012-11-29 11:35 ` Simon Dawson
2012-11-29 13:53 ` Thiago A. Corrêa
2012-11-29 15:28 ` Thomas Petazzoni
2012-11-29 16:05 ` Simon Dawson
2012-11-29 16:10 ` Thiago A. Corrêa
2012-11-29 18:09 ` Thomas Petazzoni
2012-11-29 18:25 ` Thiago A. Corrêa
2012-11-29 18:31 ` Thomas Petazzoni
2012-11-29 18:48 ` Thiago A. Corrêa
2012-11-29 11:26 ` Bjørn Forsman
2012-11-29 14:58 ` David Collier
2012-11-29 15:19 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2007-08-24 13:47 [Buildroot] buildroot " Jonathan Dumaresq
2007-08-24 13:59 ` Thiago A. Corrêa
2007-08-24 14:45 ` Jonathan Dumaresq
2007-08-27 8:42 ` Hans-Christian Egtvedt
2007-08-27 19:06 ` Jonathan Dumaresq
2007-08-27 21:17 ` Bernhard Fischer
2007-08-28 13:17 ` Jonathan Dumaresq
2007-08-28 21:13 ` Bernhard Fischer
2006-08-08 21:48 [Buildroot] Buildroot for AVR32 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=20121129113710.63d5676c@skate \
--to=thomas.petazzoni@free-electrons.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