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: Mon, 28 Sep 2009 20:20:18 -0600 From: Robert Hancock <hancockrwd@...il.com> To: Luca Tettamanti <kronos.it@...il.com> Cc: lm-sensors@...sensors.org, linux-kernel@...r.kernel.org, Jean Delvare <khali@...ux-fr.org> Subject: Re: [PATCH] asus_atk0110: add support for Asus P7P55D On Mon, Sep 28, 2009 at 7:17 AM, Luca Tettamanti <kronos.it@...il.com> wrote: > On Wed, Sep 23, 2009 at 09:18:45PM -0600, Robert Hancock wrote: >> On Wed, Sep 23, 2009 at 1:12 PM, Luca Tettamanti <kronos.it@...il.com> wrote: >> > With P7P55D (and newer) boards Asus extended the output buffer (ASBF) >> > making the driver unable to read the data from the sensors. >> > Change the driver to use dynamic buffers (allocated by ACPI core); the >> > return value is cached, so the number of memory allocations is very low. >> > >> > Signed-off-by: Luca Tettamanti <kronos.it@...il.com> >> > Tested-by: Robert Hancock <hancockrwd@...il.com> >> >> I just noticed a problem (either with this patch or some other issue >> with the driver on this board): The readings don't seem to be >> updating, I get the same values all the time. (Just now I started >> compiling a kernel and coretemp reports temperatures in the 60 degree >> plus range but atk0110-acpi still reports 35 degrees as it did >> before..) > > Hi Robert, > I have a new patch for you :) > It contains the previous changes to handle the bigger ASBF buffer plus a new > method to enable the EC as suggested by Asus. Be sure to compile with > HWMON_DEBUG_CHIP enabled. Excellent.. seems to work now and give actually updating sensor readings :-) By the way, if you have any firmware-type contacts at Asus that know about these boards, you might want to point them at this problem, the BIOS DMAR tables point to invalid locations when Intel VT-d is enabled. So far haven't gotten any useful response from tech support.. http://www.gossamer-threads.com/lists/linux/kernel/1131574 -- 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