From: Gerd Hoffmann <kraxel@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] qdev: add driver class support.
Date: Fri, 10 Jul 2009 12:29:36 +0200 [thread overview]
Message-ID: <4A571810.7010606@redhat.com> (raw)
In-Reply-To: <200907101113.55407.paul@codesourcery.com>
On 07/10/09 12:13, Paul Brook wrote:
> No, but the presence of a mac address (or network backend) property tells you
> that it's a network card.
I still think that will not work for all devices.
Network cards can be identified by mac property. Ok.
Disks can be identified by a (planned) drive property (which links to
the host config). By looking at the bus you can figure this is ide,
scsi, virtio or usb-storage disk. Fine.
Serial ports, parallel ports and virtio console need a link to a
CharDriver which can be used to identify this group. But not to keep
apart serial / parallel devices.
How do you identify vga cards?
How do you identify sound cards?
How do you identify storage (scsi/ide) controllers?
How do you identify watchdog devices?
cheers,
Gerd
next prev parent reply other threads:[~2009-07-10 10:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 13:02 [Qemu-devel] [PATCH 0/5] qdev: add driver class support Gerd Hoffmann
2009-07-09 13:02 ` [Qemu-devel] [PATCH 1/5] qdev/class: core Gerd Hoffmann
2009-07-09 13:02 ` [Qemu-devel] [PATCH 2/5] qdev/class: tag sound Gerd Hoffmann
2009-07-09 13:02 ` [Qemu-devel] [PATCH 3/5] qdev/class: tag network Gerd Hoffmann
2009-07-09 13:02 ` [Qemu-devel] [PATCH 4/5] qdev/class: helper function to get a list of drivers Gerd Hoffmann
2009-07-09 13:02 ` [Qemu-devel] [PATCH 5/5] qdev/class: make pci_nic_init() use qdev's device list Gerd Hoffmann
2009-07-09 13:19 ` [Qemu-devel] [PATCH 0/5] qdev: add driver class support Paul Brook
2009-07-09 13:39 ` Gerd Hoffmann
2009-07-09 13:48 ` Paul Brook
2009-07-09 14:26 ` Gerd Hoffmann
2009-07-09 15:46 ` Anthony Liguori
2009-07-10 7:50 ` Gerd Hoffmann
2009-07-10 9:46 ` Paul Brook
2009-07-10 9:59 ` Gerd Hoffmann
2009-07-10 10:13 ` Paul Brook
2009-07-10 10:29 ` Gerd Hoffmann [this message]
2009-07-09 14:34 ` Filip Navara
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=4A571810.7010606@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 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.