-----Original Message----- From: Vojtech Pavlik [mailto:vojtech@xxxxxxx] Sent: Tuesday, July 18, 2006 4:20 PM To: Brown, Len Subject: ACPIPnP, part 2 Hi Len, The previous patch fixed some (most) machines in ECP mode. However, there are still some machines where 'rmmod parport; modprobe parport' doesn't work because of PnPACPI, resulting in this: parport: PnPBIOS parport detected. parport0: PC-style at 0x378, irq 7 [PCSPP] parport0: Printer, EPSON Stylus COLOR 640 lp0: using parport0 (interrupt-driven). parport 0x378 (WARNING): CTR: wrote 0x0c, read 0xff parport 0x378 (WARNING): DATA: wrote 0xaa, read 0xff parport 0x378: You gave this address, but there is probably no parallel port there! This means that the i/o port doesn't get enabled correctly, the same way that DMA didn't work before. I'll have to recheck that the problem still persists with the latest git snapshot, because now that I looked at the relevant functions, I see significant changes there. -- Vojtech Pavlik Director SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
