From: Lonnie Mendez <lmendez19@austin.rr.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Large USB patch
Date: Sat, 22 Apr 2006 09:36:46 -0500 [thread overview]
Message-ID: <444A3F7E.6070107@austin.rr.com> (raw)
In-Reply-To: <4449F860.1060809@gmx.de>
nix.wie.weg@gmx.de wrote:
>I have fixed this issue, also I have found the segfault on usb_del.
>Patch is attached.
>Next problem:
>Linux does not recognize it, if I add a "tablet" while linux is allready
>running. The attach is not delivered to the operating system.
>
>
Hm. There also seems to be some unchecked bounds when adding devices:
(qemu) usb_add host:001:021
Could not add USB Device 'host:001:021'
(qemu) info usb
Controller 001: uhci
001:001 = mouse
001:002 = tablet
001:001 = host:001:021
Summary: 1 USB Controller, 3 USB Devices
(qemu)
Also I've a question on where the emulated hub comes into play.
Specifically how do you currently add new devices to it? The ,addto
syntax doesn't seem to apply to the emulated hub as it takes a bus
address (the controller) and an address on the root hub. But the hub
itself would be centrally connected to a bus number identifying a
controller and not have its own. It seems we've presently traded a hub
with dynamic ports for 2 static ones. I'm glad there is a lot more
internal tracking here as with the previous system you could usb_add the
same host device several times and it wouldn't care. This should also
make it easier to reconnect the ps2 mouse when the hid mouse is dettached.
Adding a device by Vendor id and Product id doesn't seem to work. If
this is intentional then perhaps the functionality should be restored.
qemu users will find this convenient as it is a fixed/static
identification for a single usb device which is most likely going to be
the common usage.
In regards to the linux guest problem I'm not seeing it. On an older
debian SID install which is currently using linux kernel 2.6.14 all
seems well. The code here is merely the first patch combined with CVS
along with the already submitted patches. I'll try to find some
variation to test with. In which distro is this happening?
next prev parent reply other threads:[~2006-04-22 14:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 19:59 [Qemu-devel] Large USB patch nix.wie.weg
2006-04-21 2:23 ` Lonnie Mendez
2006-04-21 5:59 ` nix.wie.weg
2006-04-21 7:04 ` Lonnie Mendez
2006-04-21 14:53 ` Lonnie Mendez
2006-04-21 15:00 ` Lonnie Mendez
2006-04-21 15:50 ` Lonnie Mendez
2006-04-21 16:19 ` Lonnie Mendez
2006-04-21 16:29 ` nix.wie.weg
2006-04-21 17:28 ` Lonnie Mendez
2006-04-21 18:06 ` Lonnie Mendez
2006-04-21 18:38 ` Lonnie Mendez
2006-04-21 20:50 ` Lonnie Mendez
2006-04-22 9:33 ` nix.wie.weg
2006-04-22 14:36 ` Lonnie Mendez [this message]
2006-04-22 15:36 ` nix.wie.weg
2006-04-22 15:38 ` nix.wie.weg
2006-04-22 16:00 ` nix.wie.weg
2006-04-22 16:19 ` Lonnie Mendez
2006-04-22 16:35 ` nix.wie.weg
2006-04-23 3:38 ` Lonnie Mendez
2006-04-23 21:54 ` nix.wie.weg
2006-04-29 1:03 ` Lonnie Mendez
2006-04-29 3:29 ` Lonnie Mendez
2006-04-30 0:46 ` Lonnie Mendez
2006-04-30 20:56 ` Lonnie Mendez
2006-04-21 16:26 ` nix.wie.weg
2006-04-22 14:15 ` nix.wie.weg
2006-04-23 15:02 ` Fabrice Bellard
2006-04-23 16:11 ` nix.wie.weg
2006-04-24 23:50 ` [Qemu-devel] Update for cvs 2006-04-24 nix.wie.weg
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=444A3F7E.6070107@austin.rr.com \
--to=lmendez19@austin.rr.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).