From: Peter Feuerer <peter@piie.net>
To: Borislav Petkov <petkovbb@googlemail.com>
Cc: Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org, Andreas Mohr <andi@lisas.de>
Subject: Re: [PATCH] Acerhdf: fix fan control for BIOS 3309
Date: Sun, 05 Jul 2009 18:51:13 +0200 [thread overview]
Message-ID: <cone.1246812673.209196.4691.1000@onepiie> (raw)
In-Reply-To: <20090705135806.GB9778@liondog.tnic>
Hi Boris,
Borislav Petkov writes:
> Hi Len,
>
> please apply.
>
> ---
> From: Borislav Petkov <petkovbb@gmail.com>
> Date: Sun, 5 Jul 2009 14:35:01 +0200
> Subject: [PATCH] Acerhdf: fix fan control for BIOS 3309
>
> With BIOS update v3309, the Aspire One has had some changes to how
> the fan is being controlled. Reads to the fanreg (0x55) do not simply
> return the on/off values of the fan anymore but rather a different
> fan stage based on the current temperature. Empirically, I could
> observe the fan stage being 0x1 when booting the machine, then the
> temperature went up and the BIOS switched the fan to stage 0x2, making
> it rotate faster with final stage being fan state 0x3, aka max.
I think it was already like that before v3309. But in my opinion it doesn't
matter how fast the fan spins. As soon as it's spinning it's making too much
noise. That's why I like to use only two states for the fan, "on" (noisy,
doesn't matter how fast it's spinning) and "off" (quiet ;))
> This requires some changes to the controlling code so that it can still
> be done adequately. Also, the OFF switch has changed from 0x21 to 0x20.
> It seems almost as if they're using the least significant nibble of the
> command written to the ioport for the different fan stages.
I've been developping acerhdf with BIOS v3309 since the very beginning. And
it was working fine with 0x21 all the time. I'm going to do some further
inverstigations next few days. Thanks for reporting!
>
> While at it, convert the fancmd[] array to a real struct thus
> disambiguating command handling and making code more readable.
Good!
kind regards,
--peter
next prev parent reply other threads:[~2009-07-05 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 13:58 Borislav Petkov
2009-07-05 16:51 ` Peter Feuerer [this message]
2009-07-05 19:08 ` Andreas Mohr
2009-07-06 7:49 ` Borislav Petkov
2009-07-06 7:43 ` Borislav Petkov
2009-07-07 20:07 ` Peter Feuerer
2009-07-08 20:10 ` [PATCH] Acerhdf: 0.5.15-2 Peter Feuerer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cone.1246812673.209196.4691.1000@onepiie \
--to=peter@piie.net \
--cc=andi@lisas.de \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®