From: Robert Nelson <robert.nelson.work@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Atmel AVR32 buildroot branch
Date: Thu, 29 May 2008 17:15:32 -0500 [thread overview]
Message-ID: <483F2B04.7080709@gmail.com> (raw)
In-Reply-To: <483F1FC7.5030600@tait.co.nz>
Robin Gilks wrote:
> Where do I raise issues with the Atmel AVR32 branch of buildroot? I
> can't find a relevant mailing list/forum...
>
There is an Atmel AVR32 Buildroot Mailing list listed here along with
U-boot and Kernel mailing lists:
http://avr32linux.org/twiki/bin/view/Main/MailingLists
> If what I'm seeing is common to the main trunk perhaps someone could
> assist here...
>
> u-boot builds all the tools with the cross compiler - not very useful
> where mkimage is concerned. I eventually sorted it out manually but the
> u-boot makefile assumes all sorts of things being set in the
> environment/passed to it that it was a major PITA - it also of course
> interrupts the flow so that the kernel build fails as it doesn't get
> built with a u-image wrapper.
>
>
--
Robert Nelson
FAE - Digi-Key
prev parent reply other threads:[~2008-05-29 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 21:27 [Buildroot] Atmel AVR32 buildroot branch Robin Gilks
2008-05-29 22:15 ` Robert Nelson [this message]
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=483F2B04.7080709@gmail.com \
--to=robert.nelson.work@gmail.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