From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MLehT-0002UH-F3
	for qemu-devel@nongnu.org; Tue, 30 Jun 2009 10:52:47 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MLehO-0002NN-NE
	for qemu-devel@nongnu.org; Tue, 30 Jun 2009 10:52:47 -0400
Received: from [199.232.76.173] (port=35836 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MLehO-0002N1-HD
	for qemu-devel@nongnu.org; Tue, 30 Jun 2009 10:52:42 -0400
Received: from mx2.redhat.com ([66.187.237.31]:58401)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <quintela@redhat.com>) id 1MLehN-00019y-P6
	for qemu-devel@nongnu.org; Tue, 30 Jun 2009 10:52:42 -0400
In-Reply-To: <200906301515.45017.paul@codesourcery.com> (Paul Brook's message
	of "Tue\, 30 Jun 2009 15\:15\:43 +0100")
References: <1246361503-18254-1-git-send-email-kraxel@redhat.com>
	<m3y6r9byz3.fsf@neno.mitica>
	<200906301515.45017.paul@codesourcery.com>
From: Juan Quintela <quintela@redhat.com>
Date: Tue, 30 Jun 2009 16:49:09 +0200
Message-ID: <m3eit1bwuy.fsf@neno.mitica>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Qemu-devel] Re: [RfC PATCH] qdev: rework device properties.
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, Gerd Hoffmann <kraxel@redhat.com>

Paul Brook <paul@codesourcery.com> wrote:
>> 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.

backward compatibility?  Not that I care about this one really.

>> 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.

Yes, but it is the same problem. We are going to need something like:

-usb-hardawre name=bar,... -usbdevice disk:name=bar

or anything like that, the thing that I mean is that disk is going to
have always a parameter (what disk we mean) and mouse is not going
(necesarely)

Later, Juan.