linux-kernel - Re: [PATCH] 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]

Message-ID: <cone.1240856738.129532.5316.1000@onepiie>
Date:	Mon, 27 Apr 2009 20:25:38 +0200
From:	Peter Feuerer <peter@...e.net>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, lenb@...nel.org
Subject: Re: [PATCH] Acer Aspire One Fan Control

Hi Matthey,

thanks for your email. A modified patch will follow soon.

Matthew Garrett writes:
>> +	  For more information about this driver see
>> +	  <http://piie.net/files/acerhdf_README.txt>
> 
> Maybe include the readme in Documentation/laptop?

I would like to leave it this way for the moment.

>> +/* if you want the module to be started in kernelmode,
>> + * uncomment following line */
>> +/* #define START_IN_KERNEL_MODE */
> 
> Maybe a module parameter?

I'll leave it with the define and add the kernelmode variable to the 
parameters. This way it's easy for people who want to compile the module 
with kernelmode enabled and it's also easy for those who simply want to load 
the module.

>> +	/* silly hack - let the polling thread disable
>> +	 * kernelmode. This ensures, that the polling thread
>> +	 * doesn't switch off the fan again */
> 
> Is this still needed?

I need this hack for the new "polling" way of the thermal api. I can't 
disable polling from outside. I can change the polling delay, but the next 
polling shot is already assigned. So when I switch on the fan (to BIOS 
mode), this assigned last shot will just switch it off again (if the 
temperature is low). And then neither the BIOS nor the kernel module care 
about the fan anymore :-( The variable just prevents the last shot from 
switching off the fan.

>> +	/* print out bios data */
>> +	printk(KERN_NOTICE "acerhdf: version: %s compilation date: %s %s\n",
>> +			VERSION, __DATE__, __TIME__);
>> +	printk(KERN_NOTICE "acerhdf: biosvendor:%s\n", vendor);
>> +	printk(KERN_NOTICE "acerhdf: biosversion:%s\n", version);
>> +	printk(KERN_NOTICE "acerhdf: biosrelease:%s\n", release);
>> +	printk(KERN_NOTICE "acerhdf: biosproduct:%s\n", product);
> 
> Perhaps only do this if verbose mode is enabled? 5 lines of output for 
> one driver seems excessive.

You are right, will 2 lines in non-verbose mode be ok?

>> +		printk(KERN_NOTICE
>> +			"acerhdf: kernelmode disabled\n");
>> +		printk(KERN_NOTICE
>> +			"acerhdf: to enable kernelmode:\n");
>> +		printk(KERN_NOTICE
>> +			"acerhdf: echo -n \"enabled\" > "
>> +			"/sys/class/thermal/thermal_zone0/mode\n");
>> +		printk(KERN_NOTICE
>> +			"acerhdf: for more information read:\n");
>> +		printk(KERN_NOTICE
>> +			"acerhdf: http://piie.net/files/acerhdf_README.txt\n");
> 
> This is the default behaviour, right? So that's another 5 lines by 
> default. I don't think it's really necessary :)

I added these lines as I got lot's of emails when I set the user mode to 
default. People were complaining that the module wouldn't work, but they 
just didn't know how to switch to kernel mode and were too lazy to read the 
code or the documentation. So I think this information should stay there. I 
can try to cut it to 2 lines. Or do you have another idea to manage this?

best regards,
--peter
--
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/