Date: Fri, 19 Mar 2004 18:12:33 -0700 (MST) From: Scott Long <scottl@freebsd.org> To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no> Cc: current@freebsd.org Subject: Re: agp0 hang in 5.2.1-RELEASE Message-ID: <20040319180056.A30715@pooker.samsco.home> In-Reply-To: <xzpekro5oef.fsf@dwp.des.no> References: <20040318132321.F9436@root.org> <44ekromwds.fsf@be-well.ilk.org> <xzpish08tpl.fsf@dwp.des.no> <20040319163324.X30715@pooker.samsco.home> <xzpekro5oef.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 20 Mar 2004, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote: > Scott Long <scottl@freebsd.org> writes: > > On Fri, 19 Mar 2004, Dag-Erling [iso-8859-1] Smrgrav wrote: > > > set hint.agp.0.disabled=3D"1" > > I don't see any code in the agp drivers to look at this hint. Is this > > impleneted some other way? > > Doesn't newbus automatically take care of that? > > DES No. This has been debated occasionally, but has some landmines. Newbus doesn't know what 'agp0' is until the probe bidding is complete. So you can really only disable the attach, not the probe. But what if the probe is destructive or buggy? You're then left to telling the parent of the device (usually a bus) to ignore the device. For PCI, this requires that the user know the bus, device, and function numbers. This is inconvenient, but not impossible. Unfortunately, this also means that every bus type might have different identifiers, and no one has come up with a mechanism yet that can be logically extended to these arbitrary bus types. Maybe handling the attach phase and ignoring the probe phase is good enough for now. Feel free to propose something =3D-) Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040319180056.A30715>