From owner-acpi-jp@jp.freebsd.org  Wed Oct 18 09:40:29 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id JAA04500;
	Wed, 18 Oct 2000 09:40:29 +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 JAA04495
	for <acpi-jp@jp.freebsd.org>; Wed, 18 Oct 2000 09:40:28 +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 JAA16213
	for <acpi-jp@jp.freebsd.org>; Wed, 18 Oct 2000 09:39:11 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Message-Id: <200010180039.JAA16213@shidahara1.planet.sci.kobe-u.ac.jp>
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Tue, 17 Oct 2000 17:05:02 MST."
             <200010180005.e9I052h01148@mass.osd.bsdi.com>
Date: Wed, 18 Oct 2000 09:39:11 +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 878
Subject: [acpi-jp 878] Re: ACPI code 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

In message <200010180005.e9I052h01148@mass.osd.bsdi.com>, Mike Smith $B$5$s$$$o$/(B
:
>> In message <200010170851.e9H8ps700438@mass.osd.bsdi.com>, Mike Smith $B$5$s$$(B
>$B$o$/(B
>> :
>> >
>> >One thing I had wondered; does the ACPICA code correctly re-evaluate DATA 
>> >every time, or does it cache the result?  (And is there a useful set of 
>> >debugging flags I can turn on to watch the evaluation of this code in 
>> >order to find out what it's really doing?)
>> >
>> I  noticed that they use too few 'volatile' keyword.They only use it 
>> in assembler instruction.I  think REGION memory access always need it.
>
>The REGION stuff still uses the external access functions in 
>OsdHardware.c though, right?  Is it going to optimise across calls to 
>these functions?

Have you written some code for bus memory read/write function not I/O or PCI
configuration register in this ACPI stuff?

I think they use AcpiOsMapMemory(in OsdMemory.c) then access 
the pointer by referencing the pointer returned from the function.
(in AcpiAmlSystemMemorySpaceHandler()@amregion.c) We don't use 
bus_space_(read|write)* stuff to access memory.


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 
