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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131105125228.GB18093@kroah.com>
Date:	Tue, 5 Nov 2013 04:52:28 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Felipe Contreras <felipe.contreras@...il.com>
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: [PATCH] staging: new asus fan driver

On Tue, Nov 05, 2013 at 02:59:47AM -0600, Felipe Contreras wrote:
> Simple driver to enable control of the fan in ASUS laptops. So far this
> has only been tested in ASUS Zenbook Prime UX31A, but according to some
> online reference [1], it should work in other models as well.
> 
> The implementation is very straight-forward, the only caveat is that the
> fan speed needs to be saved after it has been manually changed because
> it won't be reported properly until it goes back to 'auto' mode.
> 
> [1] http://forum.notebookreview.com/asus/705656-fan-control-asus-prime-ux31-ux31a-ux32a-ux32vd.html
> 
> Signed-off-by: Felipe Contreras <felipe.contreras@...il.com>
> ---
> 
> Two incarnations of this code exists [1][2], one that used ACPI methods
> directly, and one through WMI. Unfortunately the WMI version needs us to pass
> physicall addresses which is not exactly clean, and that's the only reason the
> code is proposed for staging.
> 
> Most likely this cannot graduate until acpica gets support to receive virtual
> addresses.

When is that going to happen?

> 
>  [1] http://article.gmane.org/gmane.linux.power-management.general/36774
>  [2] http://article.gmane.org/gmane.linux.kernel/1576463
> 
>  drivers/staging/Kconfig                     |   2 +
>  drivers/staging/Makefile                    |   1 +
>  drivers/staging/asus-thermal/Kconfig        |   7 ++
>  drivers/staging/asus-thermal/asus_thermal.c | 166 ++++++++++++++++++++++++++++

I need a TODO file for a staging driver listing who is responsible for
it, and what is needed to be done to it in order to get it out of
staging.

thanks,

greg k-h
--
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