qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 4/4] qdev: add display capability


From: Gerd Hoffmann
Subject: Re: [Qemu-devel] [PATCH 4/4] qdev: add display capability
Date: Tue, 11 Aug 2009 18:28:46 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2

On 08/11/09 17:57, Anthony Liguori wrote:
Gerd Hoffmann wrote:
That is the case for some devices only.

A device doesn't have a capability unless it implements the backend
device interface, no?

Right.  Although that doesn't imply there is a property needed for that.

What property do you use to identify display devices?

A DisplayState * property (r/o).

Ok, that is the backend side of display devices. It would somehow make sense to export that as property like we do today for DriveInfo and CharDriverState, although there is no need right now to have that accessable as property.


What property do you use to identify sound devices?

A QEMUSoundCard * property (r/o).

That is a linked list of all sound card device instances.

What property do you use to identify watchdog devices?

A WatchdogTimerModel * property (r/o).

That is a linked list of all watchdog device models.

Why on earth these should become device properties?
That doesn't make sense to me at all.

Oh, and the WatchdogTimerModel is the one I actually want to kill off some day (after converting watchdogs to qdev). There is no need for a private device model list, we can use the qdev list instead and filter for DeviceInfo->caps & DEV_CAP_WATCHDOG.

cheers,
  Gerd





reply via email to

[Prev in Thread] Current Thread [Next in Thread]