On Sun, Mar 18, 2001 at 10:41:39PM +0000, Philip Blundell wrote:
> Richard Atterer wrote:
> >I've just set up a PLIP link between a x86 and my RiscPC. It works
> >fine, but one thing I noticed is that the 2.4 PLIP driver insists on
> >using polling and not IRQs. That is not correct behaviour, or is it?
> >The PLIP driver seems to interpret the special value "IRQ 255" as "no
> >IRQ".
>
> Do you really have a parallel port on IRQ 255? You're right that the
> driver takes this to mean that you want polled mode.
I haven't looked at the kernel source (I'm no kernel hacker anyway),
but the bit "Interrupts are ISA-Pulses" seems to imply that IRQs can
be generated, even though they are treated specially somehow:
0x278: FIFO is 16 bytes
0x278: writeIntrThreshold is 15
0x278: readIntrThreshold is 15
0x278: PWord is 8 bits
0x278: Interrupts are ISA-Pulses
0x278: ECP port cfgA=0x10 cfgB=0x40
0x278: ECP settings irq=<none or set by other means> dma=<none or set by other
means>
parport0: PC-style at 0x278 (0x678) [PCSPP,TRISTATE,COMPAT,ECP]
parport0: cpp_mux: aa55f00f52ad51(80)
parport0: cpp_daisy: aa5500ff(80)
parport0: assign_addrs: aa5500ff(80)
parport0: cpp_mux: aa55f00f52ad51(80)
parport0: cpp_daisy: aa5500ff(80)
parport0: assign_addrs: aa5500ff(80)
plip: parport0 has no IRQ. Using IRQ-less mode,which is fairly inefficient!
NET3 PLIP version 2.4-parport [EMAIL PROTECTED]
plip0: Parallel port at 0x278, not using IRQ.
The RiscPC hardware is certainly capable of generating interrupts.
Trying to force parport_pc to use e.g. IRQ 7 hangs the machine.
Cheers,
Richard (who would prefer to use PPP over lp0 instead, but...)
--
__ _
|_) /| Richard Atterer | CS student at the Technische | GnuPG key:
| \/¯| http://atterer.net | Universität München, Germany | 0x888354F7
¯ ´` ¯
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
