From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] USB serial device
Date: Thu, 17 Jan 2008 14:47:06 +0000 [thread overview]
Message-ID: <20080117144706.GE4264@implementation.uk.xensource.com> (raw)
In-Reply-To: <fb249edb0801170609g40a3fb8cxbbf551777de06a58@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
andrzej zaborowski, le Thu 17 Jan 2008 15:09:54 +0100, a écrit :
> On 13/01/2008, Samuel Thibault <samuel.thibault@eu.citrix.com> wrote:
> > Samuel Thibault, le Sun 13 Jan 2008 01:55:56 +0000, a écrit :
> > > Here is an updated version, that takes parameters, so as to be able to
> > > notably provide the product ID.
>
> Can you provide a patch to the .texi docs some time, to document these
> parameters and an example usb_add line to get the dongle detected
> under linux?
Sure, here it is.
Samuel
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1873 bytes --]
Index: qemu-doc.texi
===================================================================
RCS file: /sources/qemu/qemu/qemu-doc.texi,v
retrieving revision 1.179
diff -u -p -r1.179 qemu-doc.texi
--- qemu-doc.texi 14 Jan 2008 22:09:11 -0000 1.179
+++ qemu-doc.texi 17 Jan 2008 14:46:37 -0000
@@ -525,6 +525,10 @@ Pass through the host device identified
@item host:vendor_id:product_id
Pass through the host device identified by vendor_id:product_id (Linux only).
+@item serial:[vendorid=@var{vendor_id}][,productid=@var{product_id}]:@var{dev}
+Serial converter to host character device @var{dev}, see @code{-serial} for the
+available devices.
+
@end table
@end table
@@ -1562,7 +1566,7 @@ as necessary to connect multiple USB dev
USB devices can be connected with the @option{-usbdevice} commandline option
or the @code{usb_add} monitor command. Available devices are:
-@table @var
+@table @code
@item @code{mouse}
Virtual Mouse. This will override the PS/2 mouse emulation when activated.
@item @code{tablet}
@@ -1583,6 +1587,16 @@ above but it can be used with the tslib
coordinates it reports touch pressure.
@item @code{keyboard}
Standard USB keyboard. Will override the PS/2 keyboard (if present).
+@item @code{serial}:[vendorid=@var{vendor_id}][,product_id=@var{product_id}]:@var{dev}
+Serial converter. This emulates an FTDI FT232BM chip connected to host character
+device @var{dev}. The available character devices are the same as for the
+@code{-serial} option. The @code{vendorid} and @code{productid} options can be
+used to override the default 0403:FF00. For instance,
+@example
+usb_add serial:productid=FA00:tcp:192.168.0.2:4444
+@end example
+will connect to tcp port 4444 of ip 192.168.0.2, and plug that to the virtual
+serial converter, faking a Matrix Orbital LCD Display (USB ID 0403:FA00).
@end table
@node host_usb_devices
next prev parent reply other threads:[~2008-01-17 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 0:23 [Qemu-devel] USB serial device Samuel Thibault
2008-01-11 11:09 ` [Qemu-devel] [PATCH] " Samuel Thibault
2008-01-13 1:55 ` [Qemu-devel] " Samuel Thibault
2008-01-13 18:59 ` Samuel Thibault
2008-01-17 14:09 ` andrzej zaborowski
2008-01-17 14:47 ` Samuel Thibault [this message]
2008-01-17 22:25 ` andrzej zaborowski
2008-01-17 22:44 ` Samuel Thibault
2008-01-19 13:05 ` andrzej zaborowski
2008-01-19 21:26 ` Samuel Thibault
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=20080117144706.GE4264@implementation.uk.xensource.com \
--to=samuel.thibault@ens-lyon.org \
--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).