> -----Original Message-----
> From: Richard B. Johnson
> Sent: Friday, July 15, 2005 8:53 AM
> To: karl malbrain
> Cc: Linux-Kernel@Vger. Kernel. Org
> Subject: RE: 2.6.9: serial_core: uart_open
>
>
> On Wed, 13 Jul 2005, karl malbrain wrote:
>
> > I've also noticed that the boot sequence probes for modems on the serial
> > ports. Is it possible that 8250.c is having a problem servicing an
> > interrupt from a character/state-change left over from this
> initialization?
> >
>
> It doesn't care. Interrupts are edges in the 8250. If an interrupt
> is lost, it's just lost. The change of state gets lost or the character
> gets lost. This is rare, but cannot cause a hung system.
My spec for the NS16550D and my experience show that the specific interrupt
source identified in IIR must be serviced or the chip will initiate a new
interrupt sequence at its first opportunity.
When I wrote a 8250/16550 driver for DOS it was driven from IIR directly.
If you don't take this approach, then you must certify that each and every
path through the irq driver must service all possible interrupt sources.
karl m
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |