Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/6] upstream glibc 2.18/2.19 works fine with microblaze
Date: Mon, 28 Apr 2014 16:53:48 -0300	[thread overview]
Message-ID: <535EB1CC.8010707@zacarias.com.ar> (raw)
In-Reply-To: <CAPALihNu56_2XK5+oVrwON=pWS22xisVNTJc5Z6GX0vCvftScg@mail.gmail.com>

On 04/28/2014 04:45 PM, William Welch wrote:

> Hi again,
> 
> Thank you for your help on this -- I should have said, that I am using
> the 'git' buildroot from earlier today ( a few hours ago), with no luck
> on the native toolchain.  So am I correct, that, for example, using the
> 'git buildroot', then ' make qemu_microblazeel_mmu_defconfig'  should
> build the native toolchain and the resulting image should boot?  Or,
> maybe the patches are not merged into the git tree yet?
> 
> I am not very skilled with qemu, so to confirm, are the directions in
> the boards/qemu/microblazeel-mmu/readme.txt correct?  It is a little
> confusing, since they mention the s3adsp1800, whereas the system.dts
> mentions a ML505 design.  Also the readme mentions qemu 1.7.0? I have
> 1.5.0 at the moment but I can install 1.7.0 if required.
> 
> thank you,
> 
> William

Hi.
They are not merged yet, Waldemar was waiting for my gcc 4.9.x patches
to get merged (done) and is going to rebase when he has time probably.
The directions in the readme.txt are correct, i make it a habit of
testing them regularly.
I have seen different versions of Qemu failing to work properly, even if
newer or older, there's no rule for that, that's the reason i mention
the exact version there.
Unfortunately for the 2014.02 release when the toolchain changes were
shipped and the configs weren't updated so they are effectively broken
for the current toolchain (it may be that the current toolchain is
broken for real scenarios, i can't know).
Waldemar's last patch updates the qemu defconfigs to a nice and simpler
config without the need for an external dts and brings in networking
support as well.
For the "latest" i've used Qemu 2.0.0
And to make things nicer i've got a patchset that builds qemu within
buildroot to avoid the messy problem of different vesions available, it
just needs some proper docs i think and should get in, right guys? :)
Regards.

  reply	other threads:[~2014-04-28 19:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13  9:46 [Buildroot] [PATCH 0/6] Microblaze fixes Waldemar Brodkorb
2014-04-13  9:46 ` [Buildroot] [PATCH 1/6] use default binutils for microblaze Waldemar Brodkorb
2014-04-21 15:02   ` Gustavo Zacarias
2014-04-28 20:10   ` Peter Korsgaard
2014-04-13  9:46 ` [Buildroot] [PATCH 2/6] use default gcc 4.8.2 " Waldemar Brodkorb
2014-04-21 15:03   ` Gustavo Zacarias
2014-04-28 20:15   ` Peter Korsgaard
2014-04-13  9:47 ` [Buildroot] [PATCH 3/6] upstream glibc 2.18/2.19 works fine with microblaze Waldemar Brodkorb
2014-04-21 15:03   ` Gustavo Zacarias
2014-04-28 19:08     ` William Welch
2014-04-28 19:18       ` Gustavo Zacarias
2014-04-28 19:45         ` William Welch
2014-04-28 19:53           ` Gustavo Zacarias [this message]
2014-04-29  7:18           ` Waldemar Brodkorb
2014-04-29 13:14             ` Gustavo Zacarias
2014-04-29 13:27               ` Mike Zick
2014-04-28 20:17   ` Peter Korsgaard
2014-04-13  9:47 ` [Buildroot] [PATCH 4/6] disable eglibc, no time to test Waldemar Brodkorb
2014-04-21 15:03   ` Gustavo Zacarias
2014-04-13  9:47 ` [Buildroot] [PATCH 5/6] temporary hack to fix linking error Waldemar Brodkorb
2014-04-21 15:04   ` Gustavo Zacarias
2014-04-22 17:49     ` Waldemar Brodkorb
2014-04-22 18:29       ` Gustavo Zacarias
2014-04-13  9:47 ` [Buildroot] [PATCH 6/6] update to 3.14 Waldemar Brodkorb
2014-04-21 15:04   ` Gustavo Zacarias

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=535EB1CC.8010707@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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