[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120112234132.0a973cb9@pyramind.ukuu.org.uk>
Date: Thu, 12 Jan 2012 23:41:32 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Jiri Slaby <jslaby@...e.cz>
Cc: gregkh@...e.de, Arnd Bergmann <arnd@...db.de>,
alan@...ux.intel.com, linux-serial@...r.kernel.org,
jirislaby@...il.com, linux-kernel@...r.kernel.org,
"3.0 3.1 3.2" <stable@...r.kernel.org>
Subject: Re: [PATCH] TTY: fix UV serial console regression
> Unless there is some bad race in the code, the hardware seems to be
> pretty broken. Otherwise pure MSR read should not cause such a bug,
> or?
UV serial being what actual hardware and system ?
> So to prevent the bug, revert to the old behavior. I.e. read modem
> status only if we really have to -- for non-CLOCAL set serials.
> Non-CLOCAL works on this hardware OK, I tried. See? I don't.
The old behaviour is rather driver dependant eg whether it used
serial_core or not.
Doesn't look an unreasonable change though.
Alan
--
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