From: "R.L. Horn" <lists@eastcheap.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Hans-Peter Jansen <hpj@urpla.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.25.3: serial problem (minicom)
Date: Thu, 19 Jun 2008 03:20:05 -0500 (CDT) [thread overview]
Message-ID: <alpine.LNX.1.00.0806190220340.1678@hani.compact.internal> (raw)
In-Reply-To: <20080618185534.5f969f63@lxorguk.ukuu.org.uk>
On Wed, 18 Jun 2008, Alan Cox wrote:
> I don't generally work via git so I don't offhand know the changeset id.
> I guess it could do. If its causing this many actual problem cases it
> might also want to go into stable.
I vote for nipping it in the bud ASAP. There are currently eight stable
kernel versions that exhibit this bug (which I believe is fairly serious,
in breadth, if not depth), and it already has Adam Lackorzynski and me
scratching our heads trying to figure out what, if anything, to do with
minicom to accomodate it.
I would suggest one change to the 26-rc version. Rather than bypassing
tty_termios_encode_baud_rate() entirely in the B0 case, why not do
something like:
if (tty_termios_baud_rate(termios))
tty_termios_encode_baud_rate(termios, baud, baud);
else
tty_termios_encode_baud_rate(termios, 0, 0);
to ensure that c_ispeed and c_ospeed are set (just for the sake of
consistency)?
next prev parent reply other threads:[~2008-06-19 8:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 21:36 2.6.25.3: serial problem (minicom) R.L. Horn
2008-06-14 9:29 ` Alan Cox
2008-06-15 7:04 ` R.L. Horn
2008-06-16 10:13 ` Alan Cox
2008-06-17 4:22 ` R.L. Horn
2008-06-17 8:58 ` Alan Cox
2008-06-17 11:03 ` R.L. Horn
2008-06-18 0:15 ` Hans-Peter Jansen
2008-06-18 17:55 ` Alan Cox
2008-06-18 20:07 ` Olivier Galibert
2008-06-19 8:20 ` R.L. Horn [this message]
2008-06-19 23:46 ` Hans-Peter Jansen
2008-06-20 11:22 ` R.L. Horn
2008-06-17 10:50 ` R.L. Horn
-- strict thread matches above, loose matches on Subject: below --
2008-05-15 19:06 Chris Rankin
2008-05-16 3:23 ` Andrew Morton
2008-05-16 7:28 ` Chris Rankin
2008-05-16 17:33 ` Jay Cliburn
2008-05-17 12:29 ` Chris Rankin
2008-05-17 13:22 ` Jay Cliburn
2008-05-17 13:32 ` Jay Cliburn
2008-05-17 14:49 ` Chris Rankin
2008-05-17 15:10 ` Jay Cliburn
2008-05-17 18:46 ` Bart Van Assche
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=alpine.LNX.1.00.0806190220340.1678@hani.compact.internal \
--to=lists@eastcheap.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpj@urpla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox