linux-kernel - Re: Acer Aspire One fan control

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 13 Feb 2009 19:18:15 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Peter Feuerer <peter@...e.net>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Acer Aspire One fan control

On Fri, Feb 13, 2009 at 07:59:16PM +0100, Peter Feuerer wrote:
> Matthew Garrett writes:
> >If 
> >these io ports are also used by the firmware then you'll need to find 
> >ACPI methods to call to perform the fan control. 
> 
> I get the temperature by calling ec_read(0x58) and can read/write the state 
> of the fan by ec_write to / ec_read from 0x55. Actually I don't know if 
> those embedded controller registers are used by the firmware. How can I 
> find it out?

Ok, yup, that should be safe. It might be nice to implement this as an 
hwmon driver, potentially tying it into the thermal layer.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/