From: Juan Quintela <quintela@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] Re: [RfC PATCH] qdev: rework device properties.
Date: Tue, 30 Jun 2009 16:49:09 +0200 [thread overview]
Message-ID: <m3eit1bwuy.fsf@neno.mitica> (raw)
In-Reply-To: <200906301515.45017.paul@codesourcery.com> (Paul Brook's message of "Tue\, 30 Jun 2009 15\:15\:43 +0100")
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.
next prev parent reply other threads:[~2009-06-30 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 11:31 [Qemu-devel] [RfC PATCH] qdev: rework device properties Gerd Hoffmann
2009-06-30 14:03 ` [Qemu-devel] " Juan Quintela
2009-06-30 14:15 ` Paul Brook
2009-06-30 14:49 ` Juan Quintela [this message]
2009-06-30 15:11 ` Paul Brook
2009-06-30 14:19 ` Gerd Hoffmann
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=m3eit1bwuy.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=kraxel@redhat.com \
--cc=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.