qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] New device API
Date: Fri, 15 May 2009 11:40:21 +0200	[thread overview]
Message-ID: <4A0D3885.1010701@redhat.com> (raw)
In-Reply-To: <200905142239.18358.paul@codesourcery.com>

On 05/14/09 23:39, Paul Brook wrote:
> 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.

I think we should also have a generic BusState with a name and a list of 
devices attached (maybe more).  Then have "BusState *bus" instead of 
"void *bus".  Then you can actually walk the device tree in common code, 
for example have a "info devtree" monitor command printing all devices 
of the machine.

cheers,
   Gerd

  reply	other threads:[~2009-05-15  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 21:39 [Qemu-devel] New device API Paul Brook
2009-05-15  9:40 ` Gerd Hoffmann [this message]
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=4A0D3885.1010701@redhat.com \
    --to=kraxel@redhat.com \
    --cc=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).