Re: PNPACPI breaks my asus k6-2 parallel port

[Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>]

Takanori Watanabe wrote:
> In message <20041207022133.GB22171-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>, Matthew 
> Wilcox wrote:
> 
>>Turning on PNPACPI changes this in my dmesg:
>>
>>-parport0: PC-style at 0x378 [PCSPP(,...)]
>>-lp0: using parport0 (polling).
>>+ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>>+ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>>+parport: PnPBIOS parport detected.
>>+parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
>>+lp0: using parport0 (interrupt-driven).
>>+pnp: Device 00:08 activated.
>>+parport: PnPBIOS parport detected.
>>+parport1: PC-style at 0x278, irq 5 [PCSPP(,...)]
>>+lp1: using parport1 (interrupt-driven).
>>
>>As a result, my parallel port stops working.  Any more information I can
>>provide?
> 
> 
> I don't know little about Linux specific, but generally,
> a Printer port device will appear several times as ACPI devices.
> 
> If you forget to check device status (_STA), 
> confliction will occur as you got.

You are right Watanabe-san.  It appears linux just parses all resource 
sets in _PRS as separate devices instead of parsing the DPFs and 
treating them as separate sets for a single device.

-- 
Nate



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/