From: Borislav Petkov <bp@alien8.de>
To: peter@piie.net
Cc: Branislav Gajdos <brianzee@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: acerhdf.c - unsupported notebook
Date: Wed, 14 Jul 2010 08:41:41 +0200 [thread overview]
Message-ID: <20100714064141.GA5076@liondog.tnic> (raw)
In-Reply-To: <20100714072012.21363okof2qiqomc@webmail.df.eu>
From: peter@piie.net
Date: Wed, Jul 14, 2010 at 07:20:12AM +0200
> >>So that means you would keep there the definitions for Core 2 based
> >>models as well, right?
>
> The 1810's are already supported by acerhdf and some people use it
> for fan control, so we should keep it, but we should enhance the
> bios_tbl by "default_fanon" and "default_fanoff". What do you think
> Boris?
Sure, we definitely need to do that, and more specifically:
1) we have to check first with how many different types of cpus are the
1810s being shipped and
2) whether the thermal settings of those cpus differ
because if they do, you need to check for cpu types also and not only
bios version and product info, which can get very hairy very fast.
And for all those thermal settings we need official documentation and
cannot accept any other sources.
That's why I keep questioning whether it makes sense for 1810 users (or
users of something else besides acer aspire netbooks with atom cpus, for
that matter) to use this driver.
> >You still didn't answer my question whether your fan is noisy? IOW, does
> >it make sense for you to use this driver at all?
>
> Haven't got any email from a 3810 user to add support for this
> model, so for me it seems like the fan isn't noisy at all. - Usually
> as soon as a new model with a noisy fan comes out the people are
> spaming my inbox and crying ;)
What models are those, are those only aspire one netbooks or anything
else acer dumps out?
Bottom line is: I'm trying to understand what this driver should and
should not support? Frankly, I don't want to make it easy for users
to do fan control and break their hardware while doing so. Actually,
if acer's system builders would've done their job right in picking a
quieter fan for their packaging we wouldn't be talking here in the first
place. For example, I have also a lenovo edge and I almost can't hear
the fan there but that's a different story.
See what I'm sayin'?
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2010-07-14 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTin0mv0Z5vozJHkfVYCJTWMvj9JZnP_FcQ6vZBRV@mail.gmail.com>
2010-07-13 12:48 ` Borislav Petkov
2010-07-13 14:27 ` Branislav Gajdos
2010-07-13 15:13 ` Borislav Petkov
2010-07-13 17:12 ` Peter Feuerer
2010-07-13 20:30 ` Branislav Gajdos
2010-07-13 20:42 ` Borislav Petkov
2010-07-13 21:30 ` Branislav Gajdos
2010-07-14 5:20 ` peter
2010-07-14 6:41 ` Borislav Petkov [this message]
2010-07-16 22:24 ` Thomas Davis
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=20100714064141.GA5076@liondog.tnic \
--to=bp@alien8.de \
--cc=brianzee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@piie.net \
/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®