From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] qemu_ppc_mpc8544ds_defconfig does not boot
Date: Fri, 19 Jul 2013 16:55:36 -0300 [thread overview]
Message-ID: <51E999B8.2000806@zacarias.com.ar> (raw)
In-Reply-To: <CALR4fELm3cpt=x74-5fhXEr69ukbbE-Q6u_r6rS2qCbL43xVVg@mail.gmail.com>
On 07/13/2013 06:42 AM, Diego Iastrubni wrote:
> Hi all,
>
> elcuco at stimpy:~/src/buildroot$ make qemu_ppc_mpc8544ds_defconfig
> elcuco at stimpy:~/src/buildroot$ make
> elcuco at stimpy:~/src/buildroot$ qemu-system-ppc -M mpc8544ds -kernel
> output/images/vmlinux -serial stdio -net nic,model=e1000 -net user
> Unable to copy device tree in memory
> couldn't load device tree
>
> Can anyone reproduce? I am using
> cca5538556e854516a85b28ae56c06ed66427b71 (master).
Worksforme(tm) on gentoo with qemu 1.4.2.
Which qemu version and distribution? Sounds like a qemu problem to me
(maybe packaging).
Regards.
prev parent reply other threads:[~2013-07-19 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 9:42 [Buildroot] qemu_ppc_mpc8544ds_defconfig does not boot Diego Iastrubni
2013-07-19 19:55 ` Gustavo Zacarias [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=51E999B8.2000806@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