Date: Thu, 22 Apr 2010 18:49:52 +0100 From: Chris Whitehouse <cwhiteh@onetel.com> To: B J <top_gun_canada@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: "acpi_tz0: _TMP value is absurd" Message Message-ID: <4BD08C40.8010407@onetel.com> In-Reply-To: <589572.82300.qm@web30905.mail.mud.yahoo.com> References: <589572.82300.qm@web30905.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
B J wrote: > <snip> > > I created an ASL file and located what appeared to be the code block > where that value was set. I followed the statements and nothing > appeared to be unusual. (Of course, I might have missed something > because I don't have much experience with ACPI programming.) > I was able to set the temperature of hw.acpi.thermal.tz0._CRT by changing hex values in my ASL, but _CRT is hard coded whereas _TMP is set dynamically (in my ASL). There is also a problem that the value of _CRT is output by sysctl so I could watch the results of my changes, whereas _TMP is not. Which is not much help to you sorry. > One thing I did notice, however, is when I compiled that file and got > two errors arising from: > > Store (Local0, Local0) > > where Local0 hadn't been defined in that part of the code. I have no > idea how that came about, but it successfully compiled after I > commented out that statement. (A bug in the original code, perhaps?) > What happens if you recompile an unmodified ASL? I believe there is an issue that there are 2 compilers, one by microsoft, one by intel and the intel one sticks to the acpi standard whereas the MS one allows bugs. If a manufacturer only tests their acpi tables with the MS one they can have bugs. You could always write to HP and tell them it is broken and ask them to fix it haha. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BD08C40.8010407>