From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MLe7n-0007Vl-PP for qemu-devel@nongnu.org; Tue, 30 Jun 2009 10:15:55 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MLe7j-0007Ry-3D for qemu-devel@nongnu.org; Tue, 30 Jun 2009 10:15:55 -0400 Received: from [199.232.76.173] (port=43411 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MLe7i-0007Rb-IE for qemu-devel@nongnu.org; Tue, 30 Jun 2009 10:15:50 -0400 Received: from mx20.gnu.org ([199.232.41.8]:22817) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MLe7i-0007G7-9b for qemu-devel@nongnu.org; Tue, 30 Jun 2009 10:15:50 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MLe7g-0003Nk-KO for qemu-devel@nongnu.org; Tue, 30 Jun 2009 10:15:48 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Re: [RfC PATCH] qdev: rework device properties. Date: Tue, 30 Jun 2009 15:15:43 +0100 References: <1246361503-18254-1-git-send-email-kraxel@redhat.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906301515.45017.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 , Juan Quintela > What I want to do, to make usb modular I need two things: > > a- a way to defino an alias, that "mouse" is equivalent to "QEMU USB > Keyboard". One is the qdev name and the other is the name passed to > --usbdevice name. I'm not too bothered about this. We're changing the option, so I don't see any particular problem with changing the device names at the same time. > b- things like disk are composed of: > "disk" : "rest of disk arguments" > > My plan was to add both of them as properties or similar. Any better > idea? I can put it in one struct or similar, but it is not trivial > to find where to put things really, because the "mouse" part is > filled in usb-hid.c or equivalent, and the "disk" arguments part is > filled in vl.c I think this is confusing host configuration with machine configuration. This has been discussed before. Paul