public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: matthieu castet <castet.matthieu@free.fr>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Martin Doucha <next_ghost@quick.cz>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bug 11603] Re: ACPI PnP on Intel MU440EX
Date: Tue, 23 Sep 2008 23:29:22 +0200	[thread overview]
Message-ID: <48D95FB2.4050108@free.fr> (raw)
In-Reply-To: <200809221701.13569.bjorn.helgaas@hp.com>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

Bjorn Helgaas wrote:
> 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.
> 
If you want you could try to run the attached program on your pc in 
"auto/bidirectional" or "auto/EPP" mode.

This program does what _STA methods do.


Matthieu

[-- Attachment #2: lpc.c --]
[-- Type: text/x-csrc, Size: 612 bytes --]

#include <sys/io.h>

#define S707 0x0370
#define INDX S707
#define DATA S707+1


int R707(int Arg0)
{
	int ret;
	outb(0x55,INDX);
	outb(0x55,INDX);
	outb(Arg0,INDX);
	ret = inb(DATA);
	outb(0xAA,INDX);
	return ret;
}
void W707(int Arg0, int Arg1)
{
	outb(0x55,INDX);
	outb(0x55,INDX);
	outb(Arg0,INDX);
	outb(Arg1, DATA);
	outb(0xAA,INDX);
}



int GSTA()
{
	int ret;
	W707 (0x07, 0x03);
	ret = R707 (0xF0);
	printf("raw %d\n", ret);
	printf("LPT %d\n", (ret & 0x7) == 0);
	printf("EPP %d\n", (ret & 0x3) == 1);
	printf("ECP %d\n", (ret & 0x2) == 2);
	return ret;
}

int main()
{
	iopl(3);
	GSTA();
	return 0;
}

  reply	other threads:[~2008-09-23 21:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-31 13:22 ACPI PnP on Intel MU440EX 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
2008-09-23 21:29           ` matthieu castet [this message]
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=48D95FB2.4050108@free.fr \
    --to=castet.matthieu@free.fr \
    --cc=bjorn.helgaas@hp.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --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