lkml.org 
[lkml]   [1998]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: More parport troubles
On 17 Apr 1998, Andreas Muck wrote:

> I have no idea why and if it helps, but I noticed by going back to
> 2.1.88 that the parport uses IRQ 8! I'm not sure what the BIOS sais
> (I'd have to reboot to look ;) but *if* there is an IRQ in the BIOS
> I'm almost sure it's 7 (ASUS P/I-P55T2P4S).

Around about that time there was a bug in the ECP IRQ-detection code, and
it would have exactly that symptom.

> Anyway, in 2.1.88 with IRQ 8 seems to work fine.

Er.. really? Is lp actually interrupt-driven for you in 2.1.88?

> In 2.1.95 it also worked in polling mode (how does one switch to polling
> mode? I did echo "none" > /proc/parport/0/irq).

Yes, that's how, at least at the moment.

> While 2.1.95 was in IRQ mode I tried to print something - printer
> didn't move. Then I switched to polling mode (using the echo abobe)
> and it gave me a nice little Kernel Oops. It's still in a logfile
> somewhere if somebody needs it.

There were bugs in parport's /proc handling that have since been fixed. I
wouldn't mind a peek at the oops though, if you still have it (in private
email please).

> Well, I'm puzzled why 2.1.88 uses IRQ 8 and it even works with it. Let
> me know what to test out if I can help.

That 2.1.88 uses IRQ 8 isn't so surprising - that it works is.

Tim.
*/


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:42    [W:0.084 / U:0.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site