All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <oss@buserror.net>
To: Marwa Hamza <marwahamza63@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: running qemu for powerpc (32bits) architecture
Date: Fri, 03 Jun 2016 19:23:00 -0500	[thread overview]
Message-ID: <1464999780.22191.53.camel@buserror.net> (raw)
In-Reply-To: <CAGF64GXnJ-qPHo6xoueE5hPmuNFDG+n+oNWr-O1J1kaUD0zyDg@mail.gmail.com>

On Mon, 2016-05-30 at 10:04 +0100, Marwa Hamza wrote:
> hello everyone
> I'm trying to run qemu for powerpc architecture but either
> 1/ i got a black screen with this sentence " QEMU 2.4.0.1 monitor - type
> help for more information"
>                        (QEMU)
> if i run this command ./ppc-softmmu/qemu-system-ppc -M ppce500 -kernel
> ../linux-4.4.1/arch/powerpc/boot/zImage -initrd powerpc/busybox
> -1.21.0/rootfs.img.gz -append "root=/dev/ram rdinit=/bin/sh"

I can't help with the other platforms, but for ppce500, make sure you have
CONFIG_PPC_QEMU_E500 enabled in the kernel (and that it's an e500 build, of
course), pass either uImage or vmlinux (not zImage) to -kernel, and specify
the desired cpu type on the QEMU command line (using -cpu) to match the type
of kernel you built.  I recommend using e500mc rather than older e500 because
then you get standard floating point which your RFS may depend on.

Also note that this target will have a serial port for output, not a display,
so configure QEMU appropriately with -serial for how you want to access that.

If you need more help (especially with other PPC platforms) I suggest the 
qemu-ppc@nongnu.org mailing list.

-Scott

  reply	other threads:[~2016-06-04  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30  9:04 running qemu for powerpc (32bits) architecture Marwa Hamza
2016-06-04  0:23 ` Scott Wood [this message]
2016-06-05 11:32   ` Fwd: " Marwa Hamza

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=1464999780.22191.53.camel@buserror.net \
    --to=oss@buserror.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=marwahamza63@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.