From: Takanori Watanabe <takawata-yzSWc4HAx5xL9jVzuh4AOg@public.gmane.org>
To: "Li, Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: PNPACPI breaks my asus k6-2 parallel port
Date: Wed, 08 Dec 2004 11:17:18 +0900 [thread overview]
Message-ID: <200412080217.LAA15383@axe-inc.co.jp> (raw)
In-Reply-To: Your message of "Wed, 08 Dec 2004 09:08:04 +0800." <16A54BF5D6E14E4D916CE26C9AD30575BB93FB-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
In message <16A54BF5D6E14E4D916CE26C9AD30575BB93FB-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org
>, "Li, Shaohua" 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 =3D 4) is a 16550A
>>>>+ttyS1 at I/O 0x2f8 (irq =3D 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.
>Hi Nate,
>Could you please clarify it? Linux did check _STA, and only assigned
>dependent resources (that is one set of resources) from _PRS to a
>device.
>In Wilcox's case, LPT (PNP0400) has resources of 0x378, irq 7. PNPACPI
>can only assign 0x278, irq 5 to ECP (PNP0401) the resources are listed
>in ECP's _PRS. ECP possibly isn't a parport (Dunno why it said a parport
>detected), it can use DMA per the _PRS.
In many case, single Parallel port is appeared as multiple device,
like ECP port, simple parport,etc ... in ACPI name space
with only one of them activated. And if you try to wake up all resources,
only the last activated one will make available, I think.
-------------------------------------------------------
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/
next prev parent reply other threads:[~2004-12-08 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 1:08 PNPACPI breaks my asus k6-2 parallel port Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD30575BB93FB-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-12-08 2:17 ` Takanori Watanabe [this message]
[not found] ` <200412080217.LAA15383-yzSWc4HAx5xL9jVzuh4AOg@public.gmane.org>
2004-12-08 2:23 ` Li Shaohua
-- strict thread matches above, loose matches on Subject: below --
2004-12-07 2:21 Matthew Wilcox
[not found] ` <20041207022133.GB22171-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2004-12-07 2:37 ` Li Shaohua
2004-12-07 4:14 ` Takanori Watanabe
[not found] ` <200412070414.NAA01833-yzSWc4HAx5xL9jVzuh4AOg@public.gmane.org>
2004-12-07 15:40 ` Nate Lawson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200412080217.LAA15383@axe-inc.co.jp \
--to=takawata-yzswc4hax5xl9jvzuh4aog@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox