From: Greg KH <gregkh@linuxfoundation.org>
To: peter.sheeren@axiris.be
Cc: linux-serial@vger.kernel.org
Subject: Re: Fwd: Bug in USB FTDI SIO driver
Date: Sat, 8 Sep 2012 08:45:22 -0700 [thread overview]
Message-ID: <20120908154522.GA2976@kroah.com> (raw)
In-Reply-To: <20120908121439.15264wgwo05hva8f@webmail.axiris.be>
On Sat, Sep 08, 2012 at 12:14:39PM +0200, peter.sheeren@axiris.be wrote:
> Hello
>
> At the suggestion of Greg's friendly e-mail bot I'm sending my
> report to this e-mail address. I hope it's the right one.
>
> Peter
>
> Date: Sat, 08 Sep 2012 04:21:06 +0200
> From: peter.sheeren@axiris.be
> To: jhovold@gmail.com, greg@kroah.com
> Subject: Bug in USB FTDI SIO driver
>
>
> Hello
>
> I didn't find an easy way to file a bug report so I extracted the
> source file ftdi_sio.c from the latest Linux kernel and browsed for
> the e-mail addresses hence this e-mail.
>
> I've been struggling with an annoying plug-and-play issue involving
> an FT232RL-based USB device on ARM machines with Linux lately
> (including Raspberry Pi and BeagleBoard). In a nutshell the
> following is happening:
> * I plug in the FT232RL-based USB device. /dev/ttyUSB0 is created.
> * I run an application that communicate with the device via
> /dev/ttyUSB0. The application sets a baudrate - this is important.
> The application reads and writes data successfully.
> * I unplug the USB device. /dev/ttyUSB0 remains in existence - this
> is important too.
Huh? The device node should go away, as the application was told that
the device went away, is the application somehow still keeping the
device node open? If so, that's the issue here.
> * I replug the USB device. /dev/ttyUSB0 is still there.
> * I rerun the application. The application again connects with
> /dev/ttyUSB0 but it fails to transfer data. So it seems.
That's because it is trying to still talk to the old device, not the new
one, which should have showed up on ttyUSB1.
What kernel version are you using here?
greg k-h
next prev parent reply other threads:[~2012-09-08 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 10:14 Fwd: Bug in USB FTDI SIO driver peter.sheeren
2012-09-08 15:45 ` Greg KH [this message]
2012-09-08 17:16 ` Alan Cox
2012-09-08 17:20 ` peter.sheeren
2012-09-08 17:30 ` Alan Cox
2012-09-08 17:35 ` peter.sheeren
2012-09-08 17:54 ` Alan Cox
2012-09-08 18:19 ` Greg KH
2012-09-08 22:09 ` peter.sheeren
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=20120908154522.GA2976@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter.sheeren@axiris.be \
/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).