From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CFT:PATCH] 2/3: Check status of CTS when using flow control
Date: Sun, 26 Jun 2005 23:37:06 +0100 [thread overview]
Message-ID: <20050626233706.E28598@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200506261826.43244.gene.heskett@verizon.net>; from gene.heskett@verizon.net on Sun, Jun 26, 2005 at 06:26:43PM -0400
On Sun, Jun 26, 2005 at 06:26:43PM -0400, Gene Heskett wrote:
> On Sunday 26 June 2005 18:17, Russell King wrote:
> >Fix bugme #4712: read the CTS status and set hw_stopped if CTS
> >is not active.
> >
> >Thanks to Stefan Wolff for spotting this problem.
> >
> This one needs to make mainline & maybe, after 3 years, I can use a
> pl2303 to talk to an old slow coco. Twould be very nice if that
> fixed the lack of flow controls the connection apparently fails from.
Sorry, wasn't aware of the problem until recently. Reviewing the
code reveals that this bug has existed through many many many kernel
series. ;(
Have you been able to test it? You will need the first patch as well.
(also, please remember I can't send you mail directly... still.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-06-26 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 22:15 [CFT:PATCH] 1/3: Adjust serial locking Russell King
2005-06-26 22:17 ` [CFT:PATCH] 2/3: Check status of CTS when using flow control Russell King
2005-06-26 22:18 ` [CFT:PATCH] 3/3: Disable OX950 transmitter for " Russell King
2005-06-26 22:26 ` [CFT:PATCH] 2/3: Check status of CTS when using " Gene Heskett
2005-06-26 22:37 ` Russell King [this message]
2005-06-26 23:38 ` Gene Heskett
2005-06-27 8:05 ` Russell King
2005-06-27 16:40 ` Gene Heskett
2005-06-28 14:24 ` Russell King
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=20050626233706.E28598@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=gene.heskett@verizon.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.