From owner-freebsd-current@FreeBSD.ORG Wed Dec 3 11:50:24 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 865EB16A4CE; Wed, 3 Dec 2003 11:50:24 -0800 (PST) Received: from hak.cnd.mcgill.ca (hak.cnd.mcgill.ca [132.216.11.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E0D043F75; Wed, 3 Dec 2003 11:50:23 -0800 (PST) (envelope-from mat@hak.cnd.mcgill.ca) Received: from hak.cnd.mcgill.ca (localhost [127.0.0.1]) by hak.cnd.mcgill.ca (8.12.9/8.12.8) with ESMTP id hB3JlY15070595; Wed, 3 Dec 2003 14:47:34 -0500 (EST) (envelope-from mat@hak.cnd.mcgill.ca) Received: (from mat@localhost) by hak.cnd.mcgill.ca (8.12.9/8.12.8/Submit) id hB3JlXsd070594; Wed, 3 Dec 2003 14:47:33 -0500 (EST) Date: Wed, 3 Dec 2003 14:47:33 -0500 From: Mathew Kanner To: "M. Warner Losh" Message-ID: <20031203194733.GN54011@cnd.mcgill.ca> References: <20031202112236.GA77263@fit.vutbr.cz> <20031202.101425.81994360.imp@bsdimp.com> <20031202102446.S57336@pooker.samsco.home> <20031202.111148.78753608.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031202.111148.78753608.imp@bsdimp.com> User-Agent: Mutt/1.4.1i Organization: I speak for myself, operating in Montreal, CANADA X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on hak.cnd.mcgill.ca cc: cejkar@fit.vutbr.cz cc: freebsd-current@freebsd.org Subject: Re: How to disable devices in -current / 5.2-BETA? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 19:50:24 -0000 On Dec 02, M. Warner Losh wrote: > In message: <20031202102446.S57336@pooker.samsco.home> > Scott Long 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