public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* ttyS1: LSR safety check engaged! - misidentification?
@ 2007-07-29 15:26 Christian P. Schmidt
  2007-07-30 22:59 ` Andrew Morton
  0 siblings, 1 reply; 2+ messages in thread
From: Christian P. Schmidt @ 2007-07-29 15:26 UTC (permalink / raw)
  To: linux-kernel; +Cc: akpm

Hi all,

Ever since Kernel 2.6.21(rc) or so I'm plagued with this message,
disabling my serial ports that have been working perfectly from 2.6.14
till that day (and are still doing so, given that I continuously remove
the code from the source).
Actually I cannot blame the code, but it seems that on both of my
laptops the LSR is actually not readable. So, is there any plan to
remove that piece of code again, or at least change it so it can be
disabled conditionally?

Regards,
Christian

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: ttyS1: LSR safety check engaged! - misidentification?
  2007-07-29 15:26 ttyS1: LSR safety check engaged! - misidentification? Christian P. Schmidt
@ 2007-07-30 22:59 ` Andrew Morton
  0 siblings, 0 replies; 2+ messages in thread
From: Andrew Morton @ 2007-07-30 22:59 UTC (permalink / raw)
  To: Christian P. Schmidt; +Cc: linux-kernel, Russell King

On Sun, 29 Jul 2007 18:26:58 +0300
"Christian P. Schmidt" <charlie@digadd.de> wrote:

> Hi all,
> 
> Ever since Kernel 2.6.21(rc) or so I'm plagued with this message,
> disabling my serial ports that have been working perfectly from 2.6.14
> till that day (and are still doing so, given that I continuously remove
> the code from the source).
> Actually I cannot blame the code, but it seems that on both of my
> laptops the LSR is actually not readable. So, is there any plan to
> remove that piece of code again, or at least change it so it can be
> disabled conditionally?
> 

afaict this code:

	/*
	 * At this point, there's no way the LSR could still be 0xff;
	 * if it is, then bail out, because there's likely no UART
	 * here.
	 */
	if (!(up->port.flags & UPF_BUGGY_UART) &&
	    (serial_inp(up, UART_LSR) == 0xff)) {
		printk("ttyS%d: LSR safety check engaged!\n", up->port.line);
		return -ENODEV;
	}

is unchanged since 2.6.1, so I'm unsure what change you're proposing here?


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-07-30 23:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-07-29 15:26 ttyS1: LSR safety check engaged! - misidentification? Christian P. Schmidt
2007-07-30 22:59 ` Andrew Morton

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox