All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Dushyant Bansal <cs5070214@cse.iitd.ac.in>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Emulating powerpc 440EP with qemu-system-ppcemb
Date: Sun, 23 Jan 2011 13:21:54 -0600	[thread overview]
Message-ID: <4D3C7FD2.1020909@landley.net> (raw)
In-Reply-To: <4D3C7AEE.2020204@cse.iitd.ac.in>

On 01/23/2011 01:01 PM, Dushyant Bansal wrote:
> I am also using
> <http://www.landley.net/aboriginal/downloads/binaries/cross-compiler-powerpc-440fp.tar.bz2>"cross-compiler-powerpc-440fp"
> from the aboriginal project
> (http://www.landley.net/aboriginal/downloads/binaries/) to build the
> kernel image :).

Heh. :)

Note that I don't have any actual ppc440 hardware.  Somebody else once
tested this on real hardware for me and said it worked (their interest
was why i added the platform in the first place), and I haven't changed
the compiler config since then, but I can't prove anything if QEMU won't
cooperate.

> Yes, qemu supports ppc440(bamboo).
> 
> $ qemu-system-ppcemb -M ?
> Supported machines are:
> mpc8544ds  mpc8544ds
> bamboo     bamboo
> ref405ep   ref405ep
> taihu      taihu
> mac99      Mac99 based PowerMAC
> g3beige    Heathrow based PowerMAC (default)
> prep       PowerPC PREP platform

Those are board emulations.  Does it have a 440 _cpu_ emulation?

./qemu-system-ppc -cpu ? | grep 440

(Don't ask me why qemu-system-ppc lists every single powerpc stepping
ever as a separate interesting CPU emulation.  Seems kind of crazy to
me, but eh...)

>> What kernel .config are you using for the bamboo kernel?
> I am using arch/powerpc/configs/44x/bamboo_defconfig.

Reasonable.

Note that beating a usable console out of the thing so you can see
output is the second hard step.  (The first hard step is getting
everything set up so that the kernel will actually build and boot on the
hardware.  Without a console, you can't prove it did.)

I prefer serial console to pop-up window because it's scriptable with
"expect" or similar, I can log the output via "tee", and cut and paste
works without further effort.  But if you're just trying to see boot
messages, a SDL frame buffer window (or vnc) is fine.

Rob

  reply	other threads:[~2011-01-23 19:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-23 12:59 [Qemu-devel] Emulating powerpc 440EP with qemu-system-ppcemb Dushyant Bansal
2011-01-23 18:42 ` Rob Landley
2011-01-23 19:01   ` Dushyant Bansal
2011-01-23 19:21     ` Rob Landley [this message]
2011-01-23 19:52       ` Dushyant Bansal
2011-01-23 22:21         ` Rob Landley
2011-01-23 19:52   ` Andreas Färber
2011-01-23 20:08     ` Dushyant Bansal
2011-01-23 21:00       ` Edgar E. Iglesias
2011-01-23 22:11     ` Alexander Graf

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=4D3C7FD2.1020909@landley.net \
    --to=rob@landley.net \
    --cc=cs5070214@cse.iitd.ac.in \
    --cc=qemu-devel@nongnu.org \
    /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.