From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] New device API
Date: Thu, 14 May 2009 22:39:18 +0100 [thread overview]
Message-ID: <200905142239.18358.paul@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
I've just pushed out changes implementing a new device API.
This is based on my previous RFC[1], but with a few changes. The main one
being increased used of proxies/wrappers to implement common bus
functionality. For example there are frameworks for PCI, "ISA"[1] and I2C
devices all built on top of a common core.
There's a fair amount still needs to be converted, but I'm reasonably happy
that it is headed in the right direction. Hopefully most of it should be
fairly self-explanatory.
Next up is actual config driven machine creation.
Paul
[1] http://lists.gnu.org/archive/html/qemu-devel/2009-05/msg00210.html
[2] In this context ISA == any device connected to the main cpu/system bus.
[-- Attachment #2: Type: text/html, Size: 2078 bytes --]
next reply other threads:[~2009-05-14 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 21:39 Paul Brook [this message]
2009-05-15 9:40 ` [Qemu-devel] New device API Gerd Hoffmann
2009-05-15 15:19 ` Gerd Hoffmann
2009-05-22 23:16 ` Paul Brook
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=200905142239.18358.paul@codesourcery.com \
--to=paul@codesourcery.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).