On Fri, 8 Dec 2000, Chad R. Larson wrote: > I'm not trying to foster a war here. There seems to be enough of > that anyway. But unless this PCI register reading thingie is an > issue for i386 boxen (and I don't think it is) we shouldn't cripple > functionality on the i386 for the Alpha. Allowing programs direct access to hardware is Windows 95's thing, though. We don't want to tread on its turf. Seriously, though. There must be some way to abuse such direct access to the pci configuration registers. Just because nobody has figured it out how yet doesn't mean that enabling the feature is a good idea. Mike "Silby" Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- PCIOCGETCONF/PCIOCREAD requires write permission? Lyndon Nerenberg
- Re: PCIOCGETCONF/PCIOCREAD requires write permiss... Kenneth D. Merry
- Re: PCIOCGETCONF/PCIOCREAD requires write per... Andrew Gallatin
- Re: PCIOCGETCONF/PCIOCREAD requires write... Matthew Jacob
- Re: PCIOCGETCONF/PCIOCREAD requires w... Chad R. Larson
- Re: PCIOCGETCONF/PCIOCREAD requi... Warner Losh
- Re: Re: PCIOCGETCONF/PCIOCREAD r... Mike Silbersack
- Re: Re: PCIOCGETCONF/PCIOCRE... Stefan Esser
- Re: PCIOCGETCONF/PCIOCREAD requi... David O'Brien
- Re: PCIOCGETCONF/PCIOCREAD r... Daniel C. Sobral
- Re: PCIOCGETCONF/PCIOCRE... Wes Peters
- Re: PCIOCGETCONF/PCIOCRE... Dag-Erling Smorgrav
- Re: PCIOCGETCONF/PCIOCRE... Wes Peters
- Re: PCIOCGETCONF/PCIOCREAD r... Warner Losh
- Re: PCIOCGETCONF/PCIOCRE... Daniel C. Sobral
- Re: PCIOCGETCONF/PCIOCRE... Wes Peters
- Re: PCIOCGETCONF/PCIOCREAD requires write... Peter Wemm