From owner-acpi-jp@jp.freebsd.org  Wed Jul  5 20:45:00 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id UAA92359;
	Wed, 5 Jul 2000 20:45:00 +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 UAA92354
	for <acpi-jp@jp.freebsd.org>; Wed, 5 Jul 2000 20:45:00 +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.1+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e65Biwp46792
	for <acpi-jp@jp.freebsd.org>; Wed, 5 Jul 2000 20:44:58 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
From: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>
To: blind-copy-recipients:;
X-Dispatcher: imput version 20000228(IM140)
Message-Id: <20000705204455Q.iwasaki@jp.FreeBSD.org>
Date: Wed, 05 Jul 2000 20:44:55 +0900
Mime-Version: 1.0
Content-Type: Message/rfc822
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 463
Subject: [acpi-jp 463] Bcc: Re: randomdev and APM. Not working together?
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: iwasaki@jp.freebsd.org

To: haro@tk.kubota.co.jp
Cc: mark@grondar.za, current@FreeBSD.ORG
Subject: Re: randomdev and APM. Not working together? 
In-Reply-To: <20000705201216R.haro@tk.kubota.co.jp>
References: <200007010649.IAA13685@grimreaper.grondar.za>
	<20000705145916I.haro@tk.kubota.co.jp>
	<20000705201216R.haro@tk.kubota.co.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: <20000705204455R.iwasaki@jp.FreeBSD.org>
Date: Wed, 05 Jul 2000 20:44:55 +0900
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 19

> I think I found the problem, and being able to work around it. 
> But, I don't know how to realy fix it.

I noticed this when I saw your last message :-)

>  2)Randomdev Loaded: Probe & attach will happen in the order -
>    (1)acpi0, (2)apm0, (3)nxp0 .....NG
> 
>    Because acpi0 access the BIOS first, APM support in BIOS seems to
>    get turned off. :-(

Yes, current acpi driver is doing this for testing purpose in
attach().  We need to handle this matter soon so that we could have
both of apm and acpi in our kernel.  Could you disable this line in
sys/i386/acpi/acpi.c:acpi_attach() and enable acpi later with acpiconf -e ?

	acpi_enable_disable(sc, 1);

Thanks
