Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 31 Aug 2005 19:57:36 +0200
From:      "Philip S. Schulz" <ph.schulz@gmx.de>
To:        Ulrich Spoerlein <q@galgenberg.net>
Cc:        freebsd-mobile@freebsd.org
Subject:   Disabling device probing (was: Re: long flight; need battery power!)
Message-ID:  <4315EF90.2080709@gmx.de>
In-Reply-To: <20050831145150.GA1050@galgenberg.net>
References:  <430E4967.20355.1BF72257@localhost>	<e367ea1005082604092c3fe807@mail.gmail.com>	<20050826162107.GB659@obiwan.tataz.chchile.org>	<430F536A.5060008@gmx.de> <20050831145150.GA1050@galgenberg.net>

next in thread | previous in thread | raw e-mail | index | archive | help
on 31.08.2005 16:51 Uhr Ulrich Spoerlein said the following:
> On Fri, 26.08.2005 at 19:37:46 +0200, Philip S. Schulz wrote:
> 
>>[relative cpufreq drivers suck]
>>
>>  Personally, I find this very annoying b/c 750 MHz makes the fan spin up more often than 
>>800 MHz where I don't feel any difference in performance.
>>
>>  In order to work only with absulute drivers, i.e. emulate the est(4) behaviour, use 
>>/boot/device.hints to disable all relative drivers your system detects.
> 
> 
> I have the same problem and am still running est/estctrl on my 6.0
> Banias-Laptop. I read cpufreq(4) and didn't find any documented loader
> tunables.  Would you care to share the magic incantation, that disables
> relative drivers?
> 

most (all?) drivers don't probe for the hardware if you set the variable 
hint.[device].[instance].disabled="1". For example, to disable probing 
for p4tcc0, I have hint.p4tcc.0.disabled="1" in /boot/device.hints

Regards,

Phil.

-- 

Don't fix it if it ain't broke.



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