Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 6 Oct 2010 17:48:09 +1100
From:      Alexander Kojevnikov <alexander@kojevnikov.com>
To:        freebsd-current@freebsd.org
Cc:        Bruce Cran <bruce@cran.org.uk>, spawk@acm.poly.edu
Subject:   Re: sysctl debug.cpufreq.highest
Message-ID:  <AANLkTikhQUMApXAUSCz4wKQAUtb5c5cNqKqt1ZyF5Mbo@mail.gmail.com>
In-Reply-To: <201010060718.39137.bruce@cran.org.uk>
References:  <AANLkTimk4LTze0kcoOFrfpsZmTHeOzzqv5pF%2B8cXUxKd@mail.gmail.com> <201010060718.39137.bruce@cran.org.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On 6 October 2010 17:18, Bruce Cran <bruce@cran.org.uk> wrote:
> On Wednesday 06 October 2010 03:02:36 Alexander Kojevnikov wrote:
>
>> This variable allows to underclock the CPU, which is useful when
>> building quiet or low-power systems.
>
> You can use the new -m and -M switches to powerd to control the minimum and
> maximum frequencies instead.

Thanks Bruce, now I have a good reason to upgrade to CURRENT :)

Still, it would be nice to have debug.cpufreq.highest exposed via
sysctl. Especially considering that the patch is quite short and
straightforward.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikhQUMApXAUSCz4wKQAUtb5c5cNqKqt1ZyF5Mbo>