From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Adding Microblaze support to Buildroot
Date: Tue, 22 Nov 2011 10:14:00 +0100 [thread overview]
Message-ID: <87sjlgplif.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4ECB62C8.6030301@relinux.de> (Stephan Hoffmann's message of "Tue, 22 Nov 2011 09:52:24 +0100")
>>>>> "Stephan" == Stephan Hoffmann <sho@relinux.de> writes:
Stephan> Hello all,
Stephan> is there an interest in adding the Microblaze architecture to
Stephan> buildroot?
Yes, I would say so.
Stephan> And, if it is, would it be acceptable to rely on toolchain
Stephan> and/or bootloader coming from the board vendor or Xilinx, at
Stephan> least for some time?
We're doing that already for avr32, so that's not really a big
problem. I'm more worrying about how much we need to patch individual
packages to work on microblaze. In the past we had quite some avr32
patches, which made it harder to move to newer versions and added extra
complexity to BR.
But as long as the microblaze developers work on getting their changes
upstream, I don't have a problem with adding microblaze support.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-11-22 9:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EBC554E.7050605@gmail.com>
2011-11-10 22:55 ` [Buildroot] Adding Microblaze support to Buildroot Spenser Gilliland
2011-11-11 12:45 ` Stephan Hoffmann
2011-11-22 8:52 ` Stephan Hoffmann
2011-11-22 8:58 ` Thomas Petazzoni
2011-11-22 9:07 ` Spenser Gilliland
2011-11-22 9:14 ` Peter Korsgaard [this message]
2011-11-23 11:09 ` Stephan Hoffmann
2011-11-23 13:54 ` Thomas Petazzoni
2011-11-23 15:46 ` Stephan Hoffmann
2011-11-23 15:49 ` Thomas Petazzoni
2011-11-23 17:06 ` Stephan Hoffmann
2011-11-27 17:38 ` [Buildroot] [PATCH] " Stephan Hoffmann
2011-11-28 5:26 ` Baruch Siach
2012-02-11 4:58 ` Spenser Gilliland
2012-02-11 16:18 ` Arnout Vandecappelle
2012-02-12 22:44 ` Spenser Gilliland
2012-02-13 1:03 ` [Buildroot] [PATCH] Added microblaze patch Spenser Gilliland
2012-02-13 21:37 ` Arnout Vandecappelle
2012-02-14 0:07 ` Spenser Gilliland
2012-02-14 3:50 ` Spenser Gilliland
2012-02-14 5:02 ` Spenser Gilliland
2012-02-14 17:15 ` Arnout Vandecappelle
2012-02-16 21:28 ` Spenser Gilliland
2012-02-18 11:16 ` Arnout Vandecappelle
2012-02-18 23:34 ` Spenser Gilliland
2012-02-14 9:22 ` Alvaro Gamez
2012-02-14 9:49 ` Peter Korsgaard
2012-02-14 9:56 ` [Buildroot] [PATCH] DOWNLOAD_WGET: use -O instead of -P to set output file Arnout Vandecappelle
2012-02-14 11:51 ` Peter Korsgaard
2012-03-11 17:04 ` [Buildroot] Added microblaze patch Stephan Hoffmann
2012-03-12 10:58 ` Alvaro Gamez
2012-03-12 18:03 ` Stephan Hoffmann
2012-03-13 22:35 ` Arnout Vandecappelle
2012-03-14 18:20 ` Stephan Hoffmann
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=87sjlgplif.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox