From owner-acpi-jp@jp.freebsd.org  Wed Feb  7 03:12:11 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id DAA59170;
	Wed, 7 Feb 2001 03:12:11 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.dis.org (mass.dis.org [216.240.45.41])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id DAA59164
	for <acpi-jp@jp.freebsd.org>; Wed, 7 Feb 2001 03:12:09 +0900 (JST)
	(envelope-from msmith@mass.dis.org)
Received: from mass.dis.org (localhost [127.0.0.1])
	by mass.dis.org (8.11.1/8.11.1) with ESMTP id f16IDT000746
	for <acpi-jp@jp.freebsd.org>; Tue, 6 Feb 2001 10:13:30 -0800 (PST)
	(envelope-from msmith@mass.dis.org)
Message-Id: <200102061813.f16IDT000746@mass.dis.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Tue, 06 Feb 2001 18:54:32 +0900."
             <200102060954.SAA65305@shidahara1.planet.sci.kobe-u.ac.jp> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 06 Feb 2001 10:13:29 -0800
From: Mike Smith <msmith@freebsd.org>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 1059
Subject: [acpi-jp 1059] Re: Problem with ACPI_TYPE_PACKAGE handling? 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> In message <200102060947.f169lie05109@mass.dis.org>, Mike Smith $B$5$s$$$o$/(B:
> >
> >In handling the _ALx objects in a ThermalZone, I'm returned an 
> >ACPI_OBJECT of ACPI_TYPE_PACKAGE by AcpiEvaluateObject that looks like 
> >this (including padding in the rest of the buffer, which is the array of 
> >objects in the Package):
> >
> >0xc0dbc640: 04 00 00 00 03 00 00 00 50 c6 db c0 00 00 00 00
> >0xc0dbc650: 00 00 00 00 00 00 00 00 c0 ea d7 c0 00 00 00 00
> >0xc0dbc660: 00 00 00 00 00 00 00 00 20 ea d7 c0 00 00 00 00
> >0xc0dbc670: 00 00 00 00 00 00 00 00 a0 e9 d7 c0 00 00 00 00
>                                      c0d7e9a0
> is ACPI_HANDLE isn't it?

Yes, it is; the problem is that the Type field in the ACPI_OBJECT is 
ACPI_TYPE_ANY, which makes it impossible to safely assumte that it's a 
Reference.

I'm not sure if the interpreter has enough context to know that the 
object is a reference - I assume it does, though, since it has to know to 
populate the Reference.Handle field.


-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E


