[lm-sensors] Could the k8temp driver be interfering with ACPI?
robert.moore at intel.com
Tue Mar 6 22:25:50 CET 2007
In other words, as per my earlier message:
Port addresses can be dynamically generated by the AML code and thus,
there is no way that the ACPI subsystem can statically predict any
addresses that will be accessed by the AML.
> -----Original Message-----
> From: linux-acpi-owner at vger.kernel.org [mailto:linux-acpi-
> owner at vger.kernel.org] On Behalf Of Pavel Machek
> Sent: Tuesday, March 06, 2007 1:21 PM
> To: Jean Delvare
> Cc: Matthew Garrett; Chuck Ebbert; Rudolf Marek; linux-
> acpi at vger.kernel.org; linux-kernel; lm-sensors at lm-sensors.org
> Subject: Re: [lm-sensors] Could the k8temp driver be interfering with
> > > > Is there anything preventing us from doing such a walk and pre-
> > > > all the I/O ranges? I am not familiar with the ACPI code at all,
> > > > you possibly propose a patch doing that?
> > >
> > > ACPI AML is probably turing-complete: I'm afraid you are trying to
> > > solve the halting problem (-> impossible).
> > Can you please translate this into something mere humans like myself
> > have a chance to understand?
> ACPI AML is turing-complete -- that means it is as powerful any
> programming language. It can do arbitrary computation. That means it
> is theoretically impossible to analyze its accesses using any program.
> Now... may be possible to introduce _some_ ACPI BIOSes, but doing it
> would certainly be very complex -- we are talking "put gcc into
> kernel" here.
> So no, it is not possible to preallocate the ranges.
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures)
> To unsubscribe from this list: send the line "unsubscribe linux-acpi"
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the lm-sensors