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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1236596081.609.9.camel@maxim-laptop>
Date:	Mon, 09 Mar 2009 12:54:41 +0200
From:	Maxim Levitsky <maximlevitsky@...il.com>
To:	Peter Feuerer <peter@...e.net>
Cc:	Ralf Hildebrandt <Ralf.Hildebrandt@...rite.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Acer Aspire One fan control

On Thu, 2009-02-12 at 22:14 +0100, Peter Feuerer wrote:
> Ralf Hildebrandt writes:
> 
> > There's a userspace program for that. So why add a kernel module?
> 
> Because you must write to and read from io-ports and I think this should be 
> done in the kernel. I guess the userspace program you are talking about is 
> acer_ec.pl? A perl script which needs very much cpu time for a 
> functionality which can be handled in kernelspace without causing any big 
> troubles.
Not just that.
While on acer one it seems that if I kill userspace script,
fan restores to its original state (eg: running), I would also
like such driver on my main notebook, which is also acer.
It fan is also controlled via EC, but 'control' is done via hack
in acpi thermal code, every time it is updated, it sends new temperature
to EC, so I can just unload acpi thermal driver, and use own
script/driver do do same job, but I afraid that usespace driver can
hung/be killed/etc leaving me without fan at all, so this why kernel
driver is better - it is more reliable.

Best regards,
	Maxim Levitsky


--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ