From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MPDOR-00089p-9D
	for qemu-devel@nongnu.org; Fri, 10 Jul 2009 06:31:51 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MPDOM-000848-8R
	for qemu-devel@nongnu.org; Fri, 10 Jul 2009 06:31:50 -0400
Received: from [199.232.76.173] (port=42547 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MPDOL-00083u-S2
	for qemu-devel@nongnu.org; Fri, 10 Jul 2009 06:31:45 -0400
Received: from mx2.redhat.com ([66.187.237.31]:56371)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1MPDOK-0000sv-SC
	for qemu-devel@nongnu.org; Fri, 10 Jul 2009 06:31:45 -0400
Message-ID: <4A571810.7010606@redhat.com>
Date: Fri, 10 Jul 2009 12:29:36 +0200
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 0/5] qdev: add driver class support.
References: <1247144544-8885-1-git-send-email-kraxel@redhat.com>
	<200907101046.22016.paul@codesourcery.com>
	<4A571102.4070503@redhat.com>
	<200907101113.55407.paul@codesourcery.com>
In-Reply-To: <200907101113.55407.paul@codesourcery.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org

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