From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MOuiH-00067f-GO for qemu-devel@nongnu.org; Thu, 09 Jul 2009 10:35:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MOuiC-00063z-8l for qemu-devel@nongnu.org; Thu, 09 Jul 2009 10:35:04 -0400 Received: from [199.232.76.173] (port=59948 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOuiC-00063t-5C for qemu-devel@nongnu.org; Thu, 09 Jul 2009 10:35:00 -0400 Received: from mail-ew0-f207.google.com ([209.85.219.207]:34107) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MOuiB-0001z4-Qx for qemu-devel@nongnu.org; Thu, 09 Jul 2009 10:35:00 -0400 Received: by ewy3 with SMTP id 3so220379ewy.34 for ; Thu, 09 Jul 2009 07:34:58 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <200907091419.11248.paul@codesourcery.com> References: <1247144544-8885-1-git-send-email-kraxel@redhat.com> <200907091419.11248.paul@codesourcery.com> Date: Thu, 9 Jul 2009 16:34:57 +0200 Message-ID: <5b31733c0907090734u5161191x6ef7fa64a29446e5@mail.gmail.com> Subject: Re: [Qemu-devel] [PATCH 0/5] qdev: add driver class support. From: Filip Navara Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org, Gerd Hoffmann On Thu, Jul 9, 2009 at 3:19 PM, Paul Brook wrote: > On Thursday 09 July 2009, Gerd Hoffmann wrote: >> =A0 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. =A0The 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 fro= m the > device properties. Plus there's no reason why a device can't implement > multiple "classes" of device. > > Paul I was just thinking about the same. There are several multi-class devices a= nd I don't see a way to represent them with this mechanism. Best regards, Filip Navara