From owner-acpi-jp@jp.freebsd.org  Wed Oct 11 15:05:06 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id PAA20716;
	Wed, 11 Oct 2000 15:05:06 +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 PAA20709
	for <acpi-jp@jp.freebsd.org>; Wed, 11 Oct 2000 15:05:05 +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 e9B651r80239
	for <acpi-jp@jp.freebsd.org>; Wed, 11 Oct 2000 15:05:01 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: acpi-jp@jp.freebsd.org
In-Reply-To: <200010110441.e9B4fAh04429@mass.osd.bsdi.com>
References: <20001010004302X.iwasaki@jp.FreeBSD.org>
	<200010110441.e9B4fAh04429@mass.osd.bsdi.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: <20001011150456A.iwasaki@jp.FreeBSD.org>
Date: Wed, 11 Oct 2000 15:04:56 +0900
From: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 51
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 850
Subject: [acpi-jp 850] Re: Any objections for ACPICA migration? 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: iwasaki@jp.freebsd.org

> > OK, everybody agreed with ACPICA migration.
> > 
> > Mike, Watanabe-san, when and how to start?  Here is my plan;
> 
> I would like to have the PCI bus integration sorted out first, and fix 
> whatever I broke with Watanabe-san's embedded controller.  Probably 
> sometime next week, I think.

OK, probably sometime next week.

> > 1. Disable acpi userland tools building (usr.sbin/Makefile) until
> >    userland porting finish. Repo-copy aml/ too.  I'll do this
> >    including porting.
> 
> I think that we should drop the aml/ stuff from the repo entirely, and 
> move back to your repo on jp.freebsd.org.  It hasn't been tagged yet, so 
> this should be OK.

I've finished porting userland tools in my hand and still need it on
the same tree in order to improve and fix ACPICA interpreter code by
comparing their implementation and behavior.  I think we're lucky
because we know two different interpreter code in detail to compare
and I believe this accelerates FreeBSD ACPI support :-)
Of course we'll concentrate on ACPICA code, but these are on the same
tree is important for me.

> > 2. Import ACPICA files as acpica device driver. (mike?)
> 
> I'll get some help doing an import of the Intel code on a vendor branch, 
> and then apply all our diffs to it.  I think that while Intel are 
> maintaining this code, we should track it this way.

Sounds good.

> > 4. Enable again acpi userland tools.
> 
> Watanabe-san also suggested that we should take some time soon to think 
> about the APIs for the userland tools.  We might want to talk about this 
> some more before settling on these tools, although I don't think that 
> should affect the migration.

Yes, acpi vs. intpm about thermal, acpi vs. apm (probabry ups?) about
power management and battery info., acpi vs. pccardd and usbd about
device attach/detachment, many thing we need to discuss...

> I do agree that we should commit soon, since I am holding everyone else 
> up with my slow patch release cycle. 8(

Not at all, I'd appreciate your hard working :-)

Thanks
