From owner-acpi-jp@jp.freebsd.org  Fri Sep  1 19:22:11 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id TAA70870;
	Fri, 1 Sep 2000 19:22:11 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tasogare.imasy.or.jp (daemon@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id TAA70860;
	Fri, 1 Sep 2000 19:22:09 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92])
	by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e81AM6r22611;
	Fri, 1 Sep 2000 19:22:07 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: acpi-jp@jp.freebsd.org, dfr@nlsystems.com
Cc: iwasaki@jp.freebsd.org, takawata@shidahara1.planet.sci.kobe-u.ac.jp,
        dfr@freebsd.org
In-Reply-To: <Pine.BSF.4.21.0009010919310.24553-100000@salmon.nlsystems.com>
References: <20000831192844V.iwasaki@jp.FreeBSD.org>
	<Pine.BSF.4.21.0009010919310.24553-100000@salmon.nlsystems.com>
X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000901192153Z.iwasaki@jp.FreeBSD.org>
Date: Fri, 01 Sep 2000 19:21:53 +0900
From: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 29
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 598
Subject: [acpi-jp 598] 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: iwasaki@jp.freebsd.org

Hi,

> > because PCI_Config region access can occur during ACPI initialisation,
> > also probing apm can be failed after switching to SCI interrupt by
> > enabling ACPI. i.e., acpi need to be probed/attached after pcib and
> > apm in this case, but should be earlier as possible for ACPI PnP.
> 
> The second argument to BUS_ADD_CHILD defines the order that the children
> are probed. The isa driver uses this to ensure that sensitive devices are
> probed early and that PnP devices are probed after all the legacy devices
> have claimed resources.

Thanks Doug, but I'm not sure whether acpi is probed before the
descendant of pcib (maybe due to be enumurated via ACPI in future).
It would be nice if we can specify the dependency on certaion devices
something like
	child = BUS_ADD_CHILD(parent, 0, "acpi", 0);
	BUS_ADD_CHILD_DEPENDENCY(parent, child, "apm");
	BUS_ADD_CHILD_DEPENDENCY(parent, child, "pcib");
to tell parent that child should be immediately fired after both "apm" and
"pcib" are initialised (before going to thier children).

Further discussions will be required when we seriously consider
integrating ACPI into the newbus probe sequence, your suggestion seems
good enough for now.  I'll modify BUS_ADD_CHILD()'s 2nd argument for
the time being.
	child = BUS_ADD_CHILD(parent, 101, "acpi", 0);	/* after pcib(100) */

Thanks Again!
