From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/4] qdev: add display capability
Date: Tue, 11 Aug 2009 10:57:13 -0500 [thread overview]
Message-ID: <4A8194D9.9040202@codemonkey.ws> (raw)
In-Reply-To: <4A817D73.4020200@redhat.com>
Gerd Hoffmann wrote:
> On 08/11/09 15:42, Anthony Liguori wrote:
>> Gerd Hoffmann wrote:
>>> ... and tag devices.
>>
>> Shouldn't there be a direct relationship between a capability and the
>> interfaces the device accepts?
>
> That is the case for some devices only.
A device doesn't have a capability unless it implements the backend
device interface, no?
That is, a device does not have the Display capability unless it returns
a DisplayState.
>> That is, instead of explicitly marking something as having a capability
>> of { "ethernet" }, wouldn't you be able to infer that from the present
>> of a VLANClientState property?
>
> Works for ethernet (well, not yet, but most likely some day ...).
>
> What property do you use to identify sound devices?
A QEMUSoundCard * property (r/o).
> What property do you use to identify display devices?
A DisplayState * property (r/o).
> What property do you use to identify watchdog devices?
A WatchdogTimerModel * property (r/o).
Regards,
Anthony Liguori
> cheers,
> Gerd
next prev parent reply other threads:[~2009-08-11 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 9:20 [Qemu-devel] [PATCH 1/4] qdev: device capabilities Gerd Hoffmann
2009-08-11 9:20 ` [Qemu-devel] [PATCH 2/4] qdev: add audio capability Gerd Hoffmann
2009-08-11 9:20 ` [Qemu-devel] [PATCH 3/4] qdev: add ethernet capability Gerd Hoffmann
2009-08-11 9:20 ` [Qemu-devel] [PATCH 4/4] qdev: add display capability Gerd Hoffmann
2009-08-11 13:42 ` Anthony Liguori
2009-08-11 14:17 ` Gerd Hoffmann
2009-08-11 15:57 ` Anthony Liguori [this message]
2009-08-11 16:28 ` Gerd Hoffmann
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=4A8194D9.9040202@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@redhat.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 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.