From: Jonathan Dumaresq <jdumaresq@cimeq.qc.ca>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot for avr32
Date: Mon, 27 Aug 2007 15:06:21 -0400 [thread overview]
Message-ID: <001001c7e8dd$5b177970$6e00a8c0@JONATHAN> (raw)
In-Reply-To: 1188204128.7890.5.camel@localhost.localdomain
Hi all,
I would like to know how to customize the kernel when i build the buildroot
for avr32 ?
make ARCH=avr32 CROSS_COMPILE=avr32-linux- menuconfig
under the linux folder don't seam to work.
Jonathan
----- Original Message -----
From: "Hans-Christian Egtvedt" <hcegtvedt@atmel.com>
To: "Thiago A. Corr?a" <thiago.correa@gmail.com>
Cc: "Jonathan Dumaresq" <jdumaresq@cimeq.qc.ca>; <buildroot@uclibc.org>
Sent: Monday, August 27, 2007 4:42 AM
Subject: Re: [Buildroot] buildroot for avr32
> On Fri, 2007-08-24 at 14:59 +0100, Thiago A. Corr?a wrote:
>> I'm using the svn buildroot with avr32, and I'm running into my
>> fair share of issues, so I guess the Atmel snapshot might be a safer
>> bet. But I really don't like that they have removed the .svn folders
>> from the package, making it a lot harder to get updates from the
>> buildroot guys. Well, svn is catching up quite rapidly, and I have
>> been able to build what I needed so far. I have never built GTK+
>> thought.
>
> I plan to put out a GIT-repository somewhere soon. There will be an
> upstream branch with the snapshots from Buildroot and a master branch
> which will hold whatever extra changes that are done for AVR32. Very
> similar to how the Linux kernel for AVR32 is available.
>
> Making diffs should be very simple if you are custom with GIT.
>
>> I have recently managed to merge the Atmel snapshot with svn to
>> some extent. But I haven't gone thru the resulting patch to sort out
>> what should be submitted and what should be discarded.
>
> The current Atmel snapshot is held at the current stage to get a stable
> base for the initial release. We try to put back the general changes
> upstream, and fiddle as little as possible away from upstream.
>
> --
> With kind regards,
> Hans-Christian Egtvedt, Applications Engineer
>
next prev parent reply other threads:[~2007-08-27 19:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 13:47 [Buildroot] buildroot for avr32 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 [this message]
2007-08-27 21:17 ` Bernhard Fischer
2007-08-28 13:17 ` Jonathan Dumaresq
2007-08-28 21:13 ` Bernhard Fischer
-- strict thread matches above, loose matches on Subject: below --
2012-11-29 10:20 [Buildroot] Buildroot " David Collier
2012-11-29 10:37 ` Thomas Petazzoni
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
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='001001c7e8dd$5b177970$6e00a8c0@JONATHAN' \
--to=jdumaresq@cimeq.qc.ca \
--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