On Fri, 16 Jul 2004, Palle Girgensohn wrote: > > --On torsdag, juli 15, 2004 20.33.28 -0400 Allan Fields <bsd_at_afields.ca> > wrote: > > > On Thu, Jul 15, 2004 at 11:36:30PM +0100, Antony T Curtis wrote: > >> On Thu, 2004-07-15 at 22:07, Palle Girgensohn wrote: > >> > Only, the flags don't work, nothing seems to happen? > > > > Did you set to ECP mode in your BIOS? > > ECP+EPP Should be fine > >> > $ kenv | grep ppc > >> > hint.ppc.0.at="isa" > >> > hint.ppc.0.flags="0xc" > >> > hint.ppc.0.irq="7" > >> > $ dmesg | grep ppc > >> > ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 > >> > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > >> > ppc0: FIFO with 16/16/16 bytes threshold > >> > ppbus0: <Parallel port bus> on ppc0 > >> > >> I must admit - I have only had it work properly when the flags was > >> compiled in the kernel config: > >> > >> device ppc0 at isa? flags 0x08 irq 7 drq 3 You shouldn't need to use flags - "lptcontrol -e" will do the job just as well. However, the key thing in that line is the "drq 3" - ECP mode will not work without a drq setting (and IIRC you just get left in SPP mode without any diagnostics). The hints listed above don't appear to include one. > > I've had ECP working in 5.1 & 5.2 using device.hints as I've been > > misusing a machine as PLIP router to provide old laptop w/ network > > since PCMCIA interface isn't working w/ installed kernel. I'm fairly sure this is irrelevant, since PLIP just does bit-bashing in the port registers that control the pins directly and doesn't use any of the parallel port modes. So, your port probably isn't really working in ECP mode but you don't care for that application. [Disclaimer: I've not really used parallel ports since 4.x, but I don't think anything of significance has changed. Certainly 'ECP must use ISA DMA' is a fundamental feature of the hardware].Received on Fri Jul 16 2004 - 08:59:41 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:02 UTC