From owner-acpi-jp@jp.freebsd.org  Tue Aug 29 17:08:48 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id RAA91538;
	Tue, 29 Aug 2000 17:08:48 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id RAA91528;
	Tue, 29 Aug 2000 17:08:44 +0900 (JST)
	(envelope-from dfr@nlsystems.com)
Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com)
	by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1)
	id 13TgRj-000PSD-0B; Tue, 29 Aug 2000 08:08:39 +0000
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA18389;
	Tue, 29 Aug 2000 09:10:11 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Tue, 29 Aug 2000 09:15:38 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: Takanori Watanabe <takawata@shidahara1.planet.sci.kobe-u.ac.jp>
cc: dfr@freebsd.org, iwasaki@jp.freebsd.org, msmith@freebsd.org,
        acpi-jp@jp.freebsd.org
In-Reply-To: <200008290653.PAA40726@shidahara1.planet.sci.kobe-u.ac.jp>
Message-ID: <Pine.BSF.4.21.0008290913090.57011-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 587
Subject: [acpi-jp 587] Re: PCI changes affect ACPI bus space access code.
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: dfr@nlsystems.com

On Tue, 29 Aug 2000, Takanori Watanabe wrote:

> Hi, now I am merging ACPI support code and I have a problem.
> 
> Due to the change to PCI-PCIB interface you made yesterday,
> Our PCI configruation access code should be modified,
> but pcib_if code  cannot be used in ACPI module because ACPI 
> module do not know about device_t of  PCI *for now*. 
> Indeed,THE RIGHT WAY is to recognize new-bus device tree to ACPI,I think,
> but it need farther discussion to be done.
> So may I export nexus_pcib_*_config functions for a time being?

Is this an ordering problem, i.e., is ACPI initialised before nexus_pcib
is created? If thats the case, then I guess it should be ok in the short
term but long term, integrating ACPI into the newbus probe sequence should
make it possible to call methods on the pcib device_t.

-- 
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 20 8348 3944


