mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Martin Doucha <next_ghost@quick.cz>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	matthieu castet <castet.matthieu@free.fr>,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bug 11603] Re: ACPI PnP on Intel MU440EX
Date: Mon, 22 Sep 2008 17:01:13 -0600	[thread overview]
Message-ID: <200809221701.13569.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200809201659.19268.bjorn.helgaas@hp.com>

Your logs are perfect, which makes me happy because it's the first
time I've successfully used the byzantine ACPI debug infrastructure.

> Log with parport set to auto/bidirectional in BIOS for comparison. PNPBIOS does
> detect it in this setting, ACPI doesn't. Same with auto/EPP which I used until
> now.

I think this is a BIOS defect.

When you set the port to "enabled" in the BIOS, Linux finds and uses
the parallel port with no problem.

When you set the port to "auto/bidirectional" or "auto/EPP" in the BIOS,
the _STA methods on all the parallel devices return 0:

     bus-0117 [00] bus_get_status        : Device [LPT] status [00000000]
     bus-0117 [00] bus_get_status        : Device [EPP] status [00000000]
     bus-0117 [00] bus_get_status        : Device [ECP] status [00000000]

A zero _STA means the device is not present at all, so I think Linux
is right to ignore the devices.

I suppose we could try to add a quirk to Linux to work around this,
but I'm not sure whether it's worth it.  Your machine is from 1998,
and some distros blacklist ACPI on old machines because it's not
worth the trouble to fix all of them.

Some drivers will blindly probe for hardware if PNP doesn't report
anything.  Is parport one of them, i.e., if you load it by hand, does
it work?

  reply	other threads:[~2008-09-22 23:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-31 13:22 Martin Doucha
2008-09-09 16:34 ` Bjorn Helgaas
2008-09-14 19:28   ` Martin Doucha
2008-09-17  5:39     ` Bjorn Helgaas
2008-09-20 22:59       ` [Bug 11603] " Bjorn Helgaas
2008-09-22 23:01         ` Bjorn Helgaas [this message]
2008-09-23 21:29           ` matthieu castet
2008-09-24 23:05             ` Bjorn Helgaas
2008-09-25 18:52               ` matthieu castet
2008-09-25 19:53                 ` Bjorn Helgaas

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=200809221701.13569.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=castet.matthieu@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=next_ghost@quick.cz \
    /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

all inboxes | Powered by JetHome®