From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding Microblaze support to Buildroot
Date: Wed, 23 Nov 2011 14:54:48 +0100 [thread overview]
Message-ID: <20111123145448.5f5d15b9@skate> (raw)
In-Reply-To: <4ECCD481.4030707@relinux.de>
Le Wed, 23 Nov 2011 12:09:53 +0100,
Stephan Hoffmann <sho@relinux.de> a ?crit :
> To which extend do you expect individual packages being tested on the
> different architectures?
On Blackfin, there are many packages that don't build, because they
simply cannot build on !MMU systems. Our goal is to progressively add
the "depends on BR2_USE_MMU" on all packages that need a MMU to
build/work properly.
So, it's definitely not a problem if not all packages have not been
tested with Microblaze. I'll add a Microblaze toolchain into my
Buildroot testing stuff, it will raise issues, and we will fix them as
we go.
> By now I have a busybox only configuration that can boot with the
> U-Boot available from the Avnet website.
>
> I can send a patch against buildroot's next branch if desired.
Excellent. Would be good to have :
* A patch adding the general Microblaze support
* A patch that adds some defconfig for the Microblaze board you have
* It would be even better if another patch could add a defconfig for
the Microblaze Qemu emulation, so that those not having a
Microblaze board can test.
Best regards,
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:[~2011-11-23 13:54 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
2011-11-23 11:09 ` Stephan Hoffmann
2011-11-23 13:54 ` Thomas Petazzoni [this message]
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=20111123145448.5f5d15b9@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 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.