atom feed11 messages in org.freebsd.freebsd-mobileDisabling device probing (was: Re: lo...
FromSent OnAttachments
Dan LangilleAug 26, 2005 2:42 am 
David LandgrenAug 26, 2005 7:55 am 
Doug HawkinsAug 26, 2005 8:39 am 
Frank AltpeterAug 26, 2005 11:09 am 
Kevin ObermanAug 26, 2005 3:54 pm 
Jeremie Le HenAug 26, 2005 4:20 pm 
Philip S. SchulzAug 26, 2005 5:37 pm 
Dan LangilleAug 30, 2005 12:20 am 
Ulrich SpoerleinAug 31, 2005 2:51 pm 
Philip S. SchulzAug 31, 2005 5:57 pm 
M. Warner LoshSep 2, 2005 1:33 pm 
Subject:Disabling device probing (was: Re: long flight; need battery power!)
From:Philip S. Schulz (ph.s@gmx.de)
Date:Aug 31, 2005 5:57:23 pm
List:org.freebsd.freebsd-mobile

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.