The receive_chars function is designed to handle the case where the port
is jammed full on by aborting after 256 characters in one IRQ.
Unfortunately the author of this code forgot that some systems are level
triggered. On these systems the IRQ simply gets invoked again and the
count loop just makes the problem take longer to clear.
In the non level case it appears that a jam could leave the IRQ jammed
forever and ignored - the remaining bytes never appearing.
As far as I can see the code would actually need to clear the interrupt
enable and then restore it on a timer event or similar in order to get
the intended effect.
Alan
-
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
