| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 21 Feb 2007 15:59:46 +0100 From: Jean Delvare <khali@...ux-fr.org> To: "Luca Tettamanti" <kronos.it@...il.com> Cc: "Matthew Garrett" <mjg59@...f.ucam.org>, linux-acpi@...r.kernel.org, linux-kernel <linux-kernel@...r.kernel.org>, "Chuck Ebbert" <cebbert@...hat.com>, lm-sensors@...sensors.org Subject: Re: [lm-sensors] Could the k8temp driver be interfering with ACPI? Hi Luca, On Tue, 20 Feb 2007 16:33:56 +0100, Luca Tettamanti wrote: > Motherboard vendors usually provide tools for $(TheOtherOS) that can > read from all thermal / fan / voltage / whatever sensors, so I guess > it's possible to make the ACPI driver and the "raw" one play nice with > each other[1]. > > Luca > [1] Unless their solution is "poke at the hardware and hope that ACPI > doesn't blow up", that is. Without the sources it's hard to tell. And all these applications are vendor-specific, so if they indeed have ways to avoid conflicting accesses between ACPI and the rest of the system, these ways are likely to be vendor-specific as well, and not documented. Either way, this means we need the support from hardware vendors to solve this concurrent access problem, and unfortunately I doubt this happens anytime soon :( -- Jean Delvare - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists