From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MOtX1-0007Nn-38 for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:19:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MOtWv-0007MS-Cz for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:19:21 -0400 Received: from [199.232.76.173] (port=42676 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOtWv-0007MP-61 for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:19:17 -0400 Received: from mx20.gnu.org ([199.232.41.8]:17239) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MOtWu-0004ob-Rb for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:19:16 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MOtWs-0003C9-J3 for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:19:14 -0400 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH 0/5] qdev: add driver class support. Date: Thu, 9 Jul 2009 14:19:10 +0100 References: <1247144544-8885-1-git-send-email-kraxel@redhat.com> In-Reply-To: <1247144544-8885-1-git-send-email-kraxel@redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907091419.11248.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Gerd Hoffmann On Thursday 09 July 2009, Gerd Hoffmann wrote: > Hi, > > This patch series brings driver classes to qdev. > > DeviceInfo gets a new field specifying what kind of device this is. > For starters there are Sound cards and Network cards. The number > of device classes will probably grow over time. > > The device class will be shown in the listing printed by '-device ?', so > users and management apps can figure what kinds of -- say -- network > cards are supported by that particular qemu binary. I'm not sure this is a good idea. You should be able to figure it out from the device properties. Plus there's no reason why a device can't implement multiple "classes" of device. Paul