From owner-acpi-jp@jp.freebsd.org  Thu Oct 12 01:16:32 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id BAA61241;
	Thu, 12 Oct 2000 01:16:32 +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 BAA61236
	for <acpi-jp@jp.freebsd.org>; Thu, 12 Oct 2000 01:16:31 +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 e9BGGTr55977
	for <acpi-jp@jp.freebsd.org>; Thu, 12 Oct 2000 01:16:29 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: acpi-jp@jp.freebsd.org
In-Reply-To: <200010090602.PAA64394@shidahara1.planet.sci.kobe-u.ac.jp>
References: <200010090509.e9959rL00685@lavender.sanpei.org>
	<200010090602.PAA64394@shidahara1.planet.sci.kobe-u.ac.jp>
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: <20001012011625K.iwasaki@jp.FreeBSD.org>
Date: Thu, 12 Oct 2000 01:16:25 +0900
From: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 12
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 853
Subject: [acpi-jp 853] Re: [report] ACPICA with MobioNX
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: iwasaki@jp.freebsd.org

> >	- apm (probe and suspend)	NG
> >		apm was not probed at boot time :-<
> 
> Shall we change probe order : apm then acpi and if apm is probed,
> disable apm and don't enable until acpi is disabled.

Hmmm, I'm sure we were able to co-exist apm and acpi with older code.
If we give up with this problem, it means retrogression...
I think we should not prevent any other device drivers from probing
during boot process if we have solutions.
How about disabling acpi at the end of the initialization for acpi, 
then enabling it from userland?  Maybe I can implement it easily.
