From owner-acpi-jp@jp.freebsd.org  Tue Oct 10 11:03:34 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id LAA03440;
	Tue, 10 Oct 2000 11:03:34 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id LAA03435
	for <acpi-jp@jp.freebsd.org>; Tue, 10 Oct 2000 11:03:34 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1])
	by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id LAA69689
	for <acpi-jp@jp.freebsd.org>; Tue, 10 Oct 2000 11:01:59 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Message-Id: <200010100201.LAA69689@shidahara1.planet.sci.kobe-u.ac.jp>
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Sun, 08 Oct 2000 05:22:12 MST."
             <200010081222.e98CMCh01218@mass.osd.bsdi.com>
Date: Tue, 10 Oct 2000 11:01:59 +0900
From: Takanori Watanabe <takawata@shidahara1.planet.sci.kobe-u.ac.jp>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 845
Subject: [acpi-jp 845] Re: Latest ACPI megapatch update
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: takawata@shidahara1.planet.sci.kobe-u.ac.jp

Oh, sorry I wrote direct mail to Mike,so I resent to acpi-jp ML.

In message <200010081222.e98CMCh01218@mass.osd.bsdi.com>, Mike Smith $B$5$s$$$o$/(B
:
>
> http://people.freebsd.org/~msmith/acpica-bsd-20001008.tar.gz
>
>New in this patch:
>
> - Fixes for the EC code (error handling)

> - Host:PCI bridges are now detected and attached using ACPI rather than
>   by rummaging in PCI configuration space.  (If this fails, we fall back
>   to the old techniques).

In my machine, EC is now *NOT* detected. It probablly due to the handling 
of device enumlation and resource management. Are you sure initialize 
resources for the device which is directly attached to acpi0?

And I found pci0 is directly attached to acpi0. I think it is *WRONG*.
acpi driver should *NOT* be act as HOST PCI BRIDGE, but act as rather 
like ISA(namely CPU ISA).

Then my *REQUEST*.
- Rename your acpi_pci.c to acpi_pcib.c and pci0 is attached to the device
defined in acpi_pcib.c . If you name the driver 'pcib', it will save 
one line for pci.c (and kldstat -v output). But if you think it confusing
convention(I think so too), I will not object to you about naming
it as 'acpi_pcib'.

- Delete pcib compatible ivar variables and move it to acpi_pcib.
(I want to remove the manipulationto get/set ACPI_HANDLE. 
And I want to add isa compatible ivar variables.)

- Fix resource handling to be sure to initialize resource.

- Print the current temperature in detected thermal zones (just cosmetic,

>   and reveals that some machines are a bit confused already).


Shall we determine API for templature meter? It is my initial interest for
ACPI ,indeed, as a author of intpm(4) .

Takanori Watanabe
<a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">
Public Key</a>
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 


