From owner-acpi-jp@jp.FreeBSD.org Wed Oct 30 01:49:35 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g9TGnZr11856;
	Wed, 30 Oct 2002 01:49:35 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tasogare.imasy.or.jp (root@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id g9TGnY311851
	for <acpi-jp@jp.FreeBSD.org>; Wed, 30 Oct 2002 01:49:34 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (iwa@tasogare.imasy.or.jp [202.227.24.5])
	by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id g9TGnWY10374;
	Wed, 30 Oct 2002 01:49:33 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Message-Id: <20021030.014927.53330880.iwasaki@jp.FreeBSD.org>
To: acpi-jp@jp.FreeBSD.org, naoki@fukaumi.org
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
In-Reply-To: <87lm4hk5eg.wl@dns1.fukaumi.org>
References: <87adl1dquq.wl@dns1.fukaumi.org>
	<20021029.145749.71081952.iwasaki@jp.FreeBSD.org>
	<87lm4hk5eg.wl@dns1.fukaumi.org>
X-Mailer: Mew version 2.2 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Wed, 30 Oct 2002 01:49:27 +0900
X-Sequence: acpi-jp 1916
Subject: [acpi-jp 1916] Re: iiyama NT310S (1/2)
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: iwasaki@jp.FreeBSD.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+021028

> I applied your 2 patch + compile error work around. But nothing was
> happend. rl0 says watchdog timeout, cbb0 can't detect card-in.
> (dmesg was changed before)

OK, please try the attached patches.

> > hw.acpi.pci.link.0.10.0.irq="3"
> > hw.acpi.pci.link.0.11.0.irq="3"
> > into your loader.conf.
> 
> I wasn't do this change. I only added acpi_dsdt_load="YES" to loader.conf.

With this configuration and PCI BIOS IRQ routing, your rl0 and cbb0 were
working fine, right?  Hmmm, this means that something is wrong with ACPI
PCI IRQ routing...

Anyone, comments?


Index: acpi_pci_link.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/acpica/acpi_pci_link.c,v
retrieving revision 1.2
diff -u -r1.2 acpi_pci_link.c
--- acpi_pci_link.c	16 Oct 2002 15:42:27 -0000	1.2
+++ acpi_pci_link.c	29 Oct 2002 16:41:57 -0000
@@ -370,7 +370,6 @@
 		ACPI_DEBUG_PRINT((ACPI_DB_WARN,
 		    "couldn't get current IRQ from PCI interrupt link %s - %s\n",
 		    acpi_name(handle), AcpiFormatException(error)));
-		goto out;
 	}
 
 	link->initial_irq = link->current_irq;
@@ -461,9 +460,9 @@
 		return_ACPI_STATUS (error);
 	}
 
-	if (!(sta & ACPI_STA_ENABLE)) {
+	if (!(sta & (ACPI_STA_PRESENT | ACPI_STA_FUNCTIONAL))) {
 		ACPI_DEBUG_PRINT((ACPI_DB_ERROR,
-		    "PCI interrupt link is disabled - %s\n",
+		    "PCI interrupt link is not functional - %s\n",
 		    acpi_name(handle)));
 		return_ACPI_STATUS (AE_ERROR);
 	}


