From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Adding Microblaze support to Buildroot
Date: Mon, 13 Feb 2012 08:59:54 +0100 [thread overview]
Message-ID: <87aa4nyxhh.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAM+bi4sKSQ80WXdZscOThUX=t18C+vMWspKWB82NWNx49gsFWw@mail.gmail.com> (Alvaro Gamez's message of "Mon, 13 Feb 2012 00:07:53 +0100")
>>>>> "Alvaro" == Alvaro Gamez <alvaro.gamez@hazent.com> writes:
Hi,
Alvaro> I am also interested on Microblaze support, hence I rescued the
Alvaro> old patch from the archives, merged it against latest git
Alvaro> revision and published on github.com /agamez/buildroot
Alvaro> I attach the new patch, should apply cleanly to latest version
Alvaro> on git.
Thanks.
Alvaro> Even though Stephan Hoffmann work is pretty good, I think the
Alvaro> path of the new files should be modified from
Alvaro> board/relinux/avnet_LX9MicroBoard/ to board/avnet/LX9MicroBoard/
I agree.
Alvaro> +++ b/configs/spartan6lx9_mb_defconfig
Alvaro> @@ -0,0 +1,17 @@
Alvaro> +BR2_microblaze=y
Alvaro> +BR2_TOOLCHAIN_EXTERNAL=y
Alvaro> +BR2_TOOLCHAIN_EXTERNAL_PATH="/opt/microblazeel-unknown-linux-gnu/"
Alvaro> +BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX="microblazeel-unknown-linux-gnu"
Is this toolchain available somewhere so I can test this?
Having a defconfig which refers to something locally on a developer
machine imho doesn't make much sense.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-02-13 7:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 23:07 [Buildroot] [PATCH] Adding Microblaze support to Buildroot Alvaro Gamez
2012-02-13 0:11 ` Spenser Gilliland
[not found] ` <CAM+bi4v0GerXFEtyM=8=gegOyuAMYjjgHx11krAoa4H2z8gOqg@mail.gmail.com>
2012-02-13 19:13 ` Alvaro Gamez
[not found] ` <CA+appbN9=yvud1LwSCpgMvUh=Qc8DoQbz=gyjfvOUmzmpsopfQ@mail.gmail.com>
2012-02-13 19:40 ` Alvaro Gamez
2012-02-13 19:46 ` Spenser Gilliland
2012-02-13 19:48 ` Alvaro Gamez
2012-02-13 19:51 ` Spenser Gilliland
2012-02-13 20:11 ` Alvaro Gamez
2012-02-13 7:59 ` Peter Korsgaard [this message]
2012-02-13 18:06 ` Stephan Hoffmann
[not found] <4EBC554E.7050605@gmail.com>
2011-11-10 22:55 ` [Buildroot] " Spenser Gilliland
2011-11-11 12:45 ` Stephan Hoffmann
2011-11-22 8:52 ` Stephan Hoffmann
2011-11-22 9:14 ` Peter Korsgaard
2011-11-23 11:09 ` Stephan Hoffmann
2011-11-23 13:54 ` Thomas Petazzoni
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
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=87aa4nyxhh.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