Date: Fri, 02 Sep 2005 07:31:23 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: ph.schulz@gmx.de Cc: q@galgenberg.net, freebsd-mobile@freebsd.org Subject: Re: Disabling device probing Message-ID: <20050902.073123.51301081.imp@bsdimp.com> In-Reply-To: <4315EF90.2080709@gmx.de> References: <430F536A.5060008@gmx.de> <20050831145150.GA1050@galgenberg.net> <4315EF90.2080709@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <4315EF90.2080709@gmx.de>
"Philip S. Schulz" <ph.schulz@gmx.de> writes:
: 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
Few, if any, device drivers don't probe if you have this hint. The
ISA bus recognizes it. Some of the newer, more experimental ones do.
I'd like to change that, but often times you have to probe the device
before you know that it is disabled...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050902.073123.51301081.imp>