Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Dec 2003 14:47:33 -0500
From:      Mathew Kanner <mat@cnd.mcgill.ca>
To:        "M. Warner Losh" <imp@bsdimp.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: How to disable devices in -current / 5.2-BETA?
Message-ID:  <20031203194733.GN54011@cnd.mcgill.ca>
In-Reply-To: <20031202.111148.78753608.imp@bsdimp.com>
References:  <20031202112236.GA77263@fit.vutbr.cz> <20031202.101425.81994360.imp@bsdimp.com> <20031202102446.S57336@pooker.samsco.home> <20031202.111148.78753608.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 02, M. Warner Losh wrote:
> In message: <20031202102446.S57336@pooker.samsco.home>
>             Scott Long <scottl@freebsd.org> writes:
> : However, having a general mechanism for disabling newbus devices would be
> : really nice.
> 
> Agreed.  But today and 5.2 you lose.  However, it isn't easy.  What
> does disabled mean?  Don't attach?  Don't even probe?  If you don't
> probe, then how do you know that the device is aac.0?  If you do
> probe, then you get ISA probe routines called that can be
> 'destructive'.

	2 cents from a newbie.  Have a pci_null driver that uses a
tunable to probe and match at a higher priority.  You would have to
know what you are looking for to avoid it, but for someone who knows
what they are doing, it would work.

	Please don't shoot me for being stupid :)

	--mat

-- 
	The state has no business in the bedrooms of the
	nation.
			- Pierre Elliott Trudeau



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