From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Alon Levy <alevy@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Should new USB devices such as usb-ccid support legacy -usbdevice?
Date: Mon, 16 May 2011 10:01:51 +0200 [thread overview]
Message-ID: <4DD0D9EF.90409@redhat.com> (raw)
In-Reply-To: <4DCD60AF.5090107@codemonkey.ws>
On 05/13/11 18:47, Anthony Liguori wrote:
> On 05/13/2011 11:36 AM, Markus Armbruster wrote:
>> When Gerd qdevified USB, he kept legacy -usbdevice working (commit
>> 0958b4cc...). What about new USB devices? Should they get a legacy
>> syntax, too?
Any reason to do that? We already have a number of devices which can be
setup via -device only, and that is perfectly fine IMHO. Also I don't
want extend the legacy syntax when adding new properties for new
features to usb devices, which will add more cases where you have to use
-device to use new features.
>> The only existing new device is usb-ccid, and it got one in commit
>> 36707144.
>
> What keeps -usbdevice from being a light wrapper to -device such that no
> future code is needed for this?
Different command line syntax. Each device (which needs/accepts
parameters) has a init function to handle the -usbdevice command line,
which basically does:
* parse old syntax
* usb_create()
* qdev_set_prop_*() calls
* qdev_init
> I know some of the names are different but presumably we could use a map
> for existing ones and pass through names for newer ones.
Just the device name is easy, there is a field in USBDeviceInfo for that
already, and in fact "-usbdevice tablet" acts like "-device usb-tablet"
thanks to that entry ;)
cheers,
Gerd
next prev parent reply other threads:[~2011-05-16 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 16:36 [Qemu-devel] Should new USB devices such as usb-ccid support legacy -usbdevice? Markus Armbruster
2011-05-13 16:47 ` Anthony Liguori
2011-05-16 8:01 ` Gerd Hoffmann [this message]
2011-05-16 8:33 ` Markus Armbruster
2011-05-17 10:37 ` Kevin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DD0D9EF.90409@redhat.com \
--to=kraxel@redhat.com \
--cc=alevy@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).