[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.1.00.0806190220340.1678@hani.compact.internal>
Date: Thu, 19 Jun 2008 03:20:05 -0500 (CDT)
From: "R.L. Horn" <lists@...tcheap.org>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
cc: Hans-Peter Jansen <hpj@...la.net>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.25.3: serial problem (minicom)
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)?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists