From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Ely Soto <Soto.Ely@orbital.com>
Subject: Re: [Qemu-devel] [PATCH] PPC32 Trace Exception and Trap instruction
Date: Fri, 29 Dec 2006 20:05:04 -0500 [thread overview]
Message-ID: <200612292005.05795.rob@landley.net> (raw)
In-Reply-To: <OF2C859C2E.49186B46-ON85257251.00599C04-85257251.005A2485@orbital.com>
On Wednesday 27 December 2006 11:24 am, Ely Soto wrote:
> Excellent, I had encountered that bug earlier on when trying to debug
> using workbench.
>
> Are you guys developing a BSP for qemu?
> I have a partially working one.
I'm poking at something like that.
http://landley.net/code/firmware
http://landley.net/hg/firmware
Of course I'm using a gcc 4.x toolchain, so I'm applying the gentoo patches to
qemu 0.8.2 to build under that, and last I checked they weren't enough to get
cvs to build under gcc 4.x, but I haven't poked at it recently...
Rob
--
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery
prev parent reply other threads:[~2006-12-30 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 16:05 [Qemu-devel] [PATCH] PPC32 Trace Exception and Trap instruction Jason Wessel
2006-12-27 16:24 ` Ely Soto
2006-12-30 1:05 ` Rob Landley [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=200612292005.05795.rob@landley.net \
--to=rob@landley.net \
--cc=Soto.Ely@orbital.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).