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:18:43 -0300	[thread overview]
Message-ID: <535EA993.8080108@zacarias.com.ar> (raw)
In-Reply-To: <CAPALihO_K2VsaYO9erhFrKZpY9755ACOjsm56O6VvxO9MA6-0Q@mail.gmail.com>

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

> Greetings,
> 
> When you say BR works fine for microblaze 'on QEMU', could you be more
> specific?  little endian?  mmu? which 'defconfig' did you use with
> buildroot?  Which version of QEMU, what command line?
> 
> I'd like to recreate your working setup and maybe that will give me a
> clue to my troubles here...
> 
> I am trying to use the 'buildroot native toolchain' with a Spartan 6
> little endian microblaze MMU design, but I don't get very far with the
> native toolchain. However, using the older 'external' toolchain boots
> linux fine.
> 
> 
> thanks,
> 
> William

Hi.
It means all relevant buildroot qemu sample defconfigs boot to a login
prompt where you can login and get dhcp working on the emulated network
(if said config has networking).
For microblaze this means big and little endian with MMU, we don't have
a nommu configuration since i've never managed to get that working in a
satisfactory way.
And that's with Waldemar's patches, not as it is right now which broke
those qemu defconfigs when the toolchain was changed to the internal
backend.
I do not know if it's the toolchain to blame and/or some Qemu
limitation, i just know that Waldemar's patches fix it for what i have
at hand (no microblaze hardware, just emulation).
Regards.

  reply	other threads:[~2014-04-28 19:18 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 [this message]
2014-04-28 19:45         ` William Welch
2014-04-28 19:53           ` Gustavo Zacarias
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=535EA993.8080108@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