From: "Andreas Färber" <afaerber@suse.de>
To: Brian Roantree <Brian.Roantree@imgtec.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] External RAM
Date: Mon, 03 Sep 2012 16:59:31 +0200 [thread overview]
Message-ID: <5044C5D3.7090805@suse.de> (raw)
In-Reply-To: <4A48AC92122C784EBD1F374BBD21766B01590421@KLMAIL01.kl.imgtec.org>
Hi,
Am 29.08.2012 15:38, schrieb Brian Roantree:
> I am using QEMU 0.15.90 to emulate a processor and have currently got it
> running in a loosely timed simulation with a systemC kernel as well,
Generally you will get more specific answers when asking about the
current code base - we're about to release v1.2.
In this case, the memory allocation (GLib), the Memory API and the
object model for devices (QOM) have all three changed significantly
since v0.15, so if you ever want to have your modifications included
upstream you'll end up redoing everything a second time almost from
scratch - which your watching boss might not be so happy about. ;)
Not sure if "SystemC kernel" is just your guest kernel or one of the
forked versions of QEMU with SystemC support, in the latter case you
should cc its maintainers on your questions and may want to poke them to
upstream their changes to avoid the diversion sketched above.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2012-09-03 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 13:38 [Qemu-devel] External RAM Brian Roantree
2012-09-01 9:26 ` Blue Swirl
2012-09-03 13:27 ` Brian Roantree
2012-09-03 14:59 ` Andreas Färber [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=5044C5D3.7090805@suse.de \
--to=afaerber@suse.de \
--cc=Brian.Roantree@imgtec.com \
--cc=blauwirbel@gmail.com \
--cc=edgar.iglesias@gmail.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).