From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] USB serial device
Date: Sat, 19 Jan 2008 14:05:20 +0100 [thread overview]
Message-ID: <fb249edb0801190505j346d740do21906d8230a88a1@mail.gmail.com> (raw)
In-Reply-To: <20080117224458.GD4300@implementation>
Hi,
On 17/01/2008, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> andrzej zaborowski, le Thu 17 Jan 2008 23:25:04 +0100, a écrit :
> > Thanks, committed although I hoped for something that lets easily test
> > that the adapter works, e.g. so that after a usb_add serial:...:stdio
> > you can do cat /dev/ttyXXXN in the guest and see what's being typed on
> > qemu's stdin. I got the device detected without problems but Linux
> > didn't create any new serial ports.
Sorry, that was a user error (mine), I had been using the generic
usb-serial.ko driver instead of the FTDI specific one. Now it indeed
works like a charm.
>
> Oh? That's odd, I've no problem here, /dev/ttyUSB0 appears like a charm
> and cat & echo work fine. We should probably use another product ID by
> default, which would be more widely automatically recognized. Here is a
> patch.
Thanks, I applied the patch even though the old values worked ok too.
If they were better for some reason please tell. I also added a
chr_close callback for -serial stdio so that I can do usb_add
serial::stdio, then usb_del and usb_add serial::stdio again without
getting an error on opening "stdio".
Cheers
next prev parent reply other threads:[~2008-01-19 13:05 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
2008-01-17 22:25 ` andrzej zaborowski
2008-01-17 22:44 ` Samuel Thibault
2008-01-19 13:05 ` andrzej zaborowski [this message]
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=fb249edb0801190505j346d740do21906d8230a88a1@mail.gmail.com \
--to=balrogg@gmail.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).