From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot-2014.05-rc3 report on Microblazeel Spartan 6 LX45 little endian uartlite and ethernetlite AXI hardware design
Date: Fri, 30 May 2014 22:03:01 +0200 [thread overview]
Message-ID: <20140530220301.47c4e2cc@free-electrons.com> (raw)
In-Reply-To: <CAPALihMP2UAY_VyxhX84Y64hb1NEWA+M9uFziw6gtmZtOi3kHw@mail.gmail.com>
Dear William Welch,
On Fri, 30 May 2014 10:58:02 -0500, William Welch wrote:
> First congratulations and thank you for all the hard work!
Thanks!
> The internal buildroot toolchain for microblazeel works fine. -- the system
> boots up into the shell prompt. Previously it had not worked on my Spartan
> 6, even though it was working on QEMU.
Cool, glad to know the recent changes made by Waldemar improved things.
> The old 'Xilinx' toolchain also works fine, as expected.
Yeah, for basic things. But we had to deprecate them because they are
causing way too many build issues with a significant number of packages.
> However, the 'MUSL' toolchain does not work -- apparently, buildroot
> quietly installs a 'big endian' toolchain, even though I selected
> microblazeel AXI. I am basing this on the output of 'readelf' on the
> kernel image and the busybox image -- both say 'big endian'. When I tried
> to boot anyway, I get no console output.
Seems like musl only supports 'microblaze', which is the BE variant of
Microblaze. I'll send a patch to adjust the Buildroot dependencies to
not offer the MUSL external toolchain on microblazeel.
Thanks a lot for the report!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-05-30 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 15:58 [Buildroot] buildroot-2014.05-rc3 report on Microblazeel Spartan 6 LX45 little endian uartlite and ethernetlite AXI hardware design William Welch
2014-05-30 19:57 ` Spenser Gilliland
2014-05-30 20:03 ` Thomas Petazzoni [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=20140530220301.47c4e2cc@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox