From: Jason Wessel <jason.wessel@windriver.com>
To: TJ <linux@tjworld.net>
Cc: qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] Add USB sys file-system support (v2)
Date: Fri, 05 Sep 2008 15:54:43 -0500 [thread overview]
Message-ID: <48C19C93.2040002@windriver.com> (raw)
In-Reply-To: <1220646531.9611.8.camel@hephaestion>
TJ wrote:
>
> I agree, maybe it is the serial character-based devices. As I can
> reproduce it with a different VID:PID of the same class it seems more
> likely.
>
The usb serial devices do not appear to have an alternate interface
and this particular ioctl will always fail for the usb serial driver
in the host kernel. It might not be the right way to fix it (see
patch below), but it does cause the device to actually work correctly
in the guest.
At this point I was able to use the rs232 usb dongle in the guest
looped back to the rs232 port on the host's motherboard via a null
modem. This means I can now debug the usb linux console driver with
qemu. :-)
Many thanks for your adding in the code to read from /dev/bus/usb.
Jason.
---
usb-linux.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/usb-linux.c
+++ b/usb-linux.c
@@ -548,8 +548,7 @@ static int usb_linux_update_endp_table(U
ret = ioctl(s->fd, USBDEVFS_CONTROL, &ct);
if (ret < 0) {
- perror("usb_linux_update_endp_table");
- return 1;
+ alt_interface = interface;
}
/* the current interface descriptor is the active interface
next prev parent reply other threads:[~2008-09-05 20:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 23:35 [Qemu-devel] [PATCH] Add USB sys file-system support TJ
2008-09-05 2:06 ` [Qemu-devel] [PATCH] Add USB sys file-system support (v2) TJ
2008-09-05 13:30 ` Jason Wessel
2008-09-05 18:51 ` TJ
2008-09-05 19:19 ` Jason Wessel
2008-09-05 20:28 ` TJ
2008-09-05 20:54 ` Jason Wessel [this message]
2008-09-05 21:13 ` [Qemu-devel] [PATCH] Add USB sys file-system support (v3) TJ
2008-09-08 14:47 ` [Qemu-devel] " Jason Wessel
2008-09-17 19:31 ` [Qemu-devel] [PATCH] Add USB sys file-system support (v4) TJ
2008-09-17 20:31 ` [Qemu-devel] " Anthony Liguori
2008-09-17 22:47 ` [Qemu-devel] [PATCH] Add USB sys file-system support (v5) TJ
2008-09-22 19:47 ` Rick Vernam
2008-09-22 22:38 ` Anthony Liguori
2008-09-25 17:34 ` Rick Vernam
2008-09-25 17:45 ` Anthony Liguori
2008-09-22 22:37 ` [Qemu-devel] " Anthony Liguori
2008-09-23 1:23 ` TJ
2008-09-23 1:33 ` [Qemu-devel] [PATCH] Add USB sys file-system support (v6) TJ
2008-09-25 17:45 ` [Qemu-devel] " Anthony Liguori
2008-09-26 13:57 ` Jason Wessel
2008-09-26 14:27 ` Anthony Liguori
2008-09-26 14:35 ` Robert Riebisch
2008-09-26 14:37 ` Anthony Liguori
2008-09-26 15:13 ` Jason Wessel
2008-09-26 15:37 ` Anthony Liguori
2008-09-30 20:53 ` TJ
2008-10-01 21:21 ` [Qemu-devel] [PATCH] Add USB sys file-system support (v7) TJ
2008-10-01 23:19 ` [Qemu-devel] [PATCH] Add USB sys file-system support (v8) TJ
2008-10-06 16:03 ` Rick Vernam
2008-10-07 8:46 ` TJ
2008-10-07 20:09 ` [Qemu-devel] " Anthony Liguori
2008-09-05 19:20 ` [Qemu-devel] [PATCH] Add USB sys file-system support (v2) TJ
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=48C19C93.2040002@windriver.com \
--to=jason.wessel@windriver.com \
--cc=kvm@vger.kernel.org \
--cc=linux@tjworld.net \
--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).