From: Greg KH <greg@kroah.com>
To: e9hack <e9hack@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Trouble with USB serial driver (ftdi_sio.c) on 2.6.31
Date: Mon, 14 Sep 2009 09:43:33 -0700 [thread overview]
Message-ID: <20090914164333.GB25381@kroah.com> (raw)
In-Reply-To: <4AAB8F3F.40403@googlemail.com>
On Sat, Sep 12, 2009 at 02:08:31PM +0200, e9hack wrote:
> Hi,
>
> I've some trouble with the USB serial driver (ftdi_sio.c for a FT232RL from FTDI). If the
> port is opened for the first time, the driver works perfectly. If the port is closed and
> open again, it isn't possible to read any data from port. Writing data to the port works.
> The FT232RL must be reconnect to get it working again. A reboot without reconnect doesn't
> solve this problem. If I look at the debug output, I don't see read requests from
> ftdi_sio.c. If reading is possible, I see this read messages:
{sigh} Yes, this driver is a bit messed up in .31, sorry. We are
working through it and hope to have a fix in one of the upcoming
.31-stable releases.
thanks,
greg k-h
next prev parent reply other threads:[~2009-09-14 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 12:08 Trouble with USB serial driver (ftdi_sio.c) on 2.6.31 e9hack
2009-09-14 16:43 ` Greg KH [this message]
2009-09-14 22:28 ` Johan Hovold
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=20090914164333.GB25381@kroah.com \
--to=greg@kroah.com \
--cc=e9hack@googlemail.com \
--cc=linux-kernel@vger.kernel.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