From owner-acpi-jp@jp.FreeBSD.org Wed Sep 11 03:47:47 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g8AIllD30991;
	Wed, 11 Sep 2002 03:47:47 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id g8AIlj330984
	for <acpi-jp@jp.FreeBSD.org>; Wed, 11 Sep 2002 03:47:46 +0900 (JST)
	(envelope-from jhb@FreeBSD.org)
Received: (qmail 27796 invoked from network); 10 Sep 2002 18:47:41 -0000
Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender <jhb@FreeBSD.org>)
          by mail12.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP
          for <iwasaki@jp.FreeBSD.org>; 10 Sep 2002 18:47:41 -0000
Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1])
	by server.baldwin.cx (8.12.5/8.12.5) with ESMTP id g8AIlVBv032391;
	Tue, 10 Sep 2002 14:47:32 -0400 (EDT)
	(envelope-from jhb@FreeBSD.org)
Message-ID: <XFMail.20020910144732.jhb@FreeBSD.org>
X-Mailer: XFMail 1.5.2 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <XFMail.20020910143954.jhb@FreeBSD.org>
From: John Baldwin <jhb@freebsd.org>
To: acpi-jp@jp.FreeBSD.org
Cc: imp@bsdimp.com, Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Tue, 10 Sep 2002 14:47:32 -0400
X-Sequence: acpi-jp 1806
Subject: [acpi-jp 1806] RE: acpi issue on my Fiva 205
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: jhb@FreeBSD.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+020902


On 10-Sep-2002 John Baldwin wrote:
> 
> On 10-Sep-2002 Mitsuru IWASAKI wrote:
>>> > I've finished writing very initial version of acpi_pci_link.c and made
>>> > some dirty hacks, then my FIVA started working on NEWCARD.
>>> > 
>>> > http://people.freebsd.org/~iwasaki/acpi/acpi_pci_link-20020910.diff
>>> > http://people.freebsd.org/~iwasaki/acpi/fiva-newcard-20020910.diff
>>> 
>>> I don't see why you need to assign the cbb interrupt via hints, that
>>> doesn't feel right at all.
>> 
>> I don't feel it's right at all too :-)
>> Because I couldn't find any functions to write cfg->inline back to PCI.
>># maybe pci_write_ivar() or new pci_write_device()?
> 
> The interrupt routing code already does that.  When we route an interrupt
> we right the value we get back to cfg->intline.

s/right/write/

>>> It seems here that only LNK7 and LNK1 are invalid, but you end up changing
>>> more LNK devices then that below.  It also seems that using IRQ's 4 and 5
>>> should be ok according to the LNK driver.
>> 
>> Yes, all LNKs have the same Possible IRQs(3, 4, 5, 7, 10, 11),
>> that looks strange for me.  And actually I tried all other possible
>> IRQs for LNK2 and 3, all failed.  Only 11 is working configuration
>> as $PIR table claimed.
> 
> Actually, if you look at the _PRT entries in your ACPI dump, all of the
> _PRT entries use an index of 0 (the 4th field in a _PRT entry) so they
> should be using the 0th interrupt (however that is done).  Well, it seems
> our current code in acpi_pcib.c doesn't fully respect SourceIndex for
> the LNK case.

Bah, I got confused a bit by what that index referred to.

> So, question: what interrupts get routed by ACPI by default right now?

Still curious.  Also, according to imp@, the non-ACPI case doesn't work either
right now, so I'd like to get that fixed first (PCIBIOS case) since it is
simpler then come back to the ACPI case.  Does anyone know how Linux handles
these machines?

-- 

John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
