[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 4/4] qdev: add display capability
From: |
Anthony Liguori |
Subject: |
Re: [Qemu-devel] [PATCH 4/4] qdev: add display capability |
Date: |
Tue, 11 Aug 2009 10:57:13 -0500 |
User-agent: |
Thunderbird 2.0.0.21 (X11/20090320) |
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