From owner-freebsd-stable Fri Dec 8 8: 2:48 2000 From owner-freebsd-stable@FreeBSD.ORG Fri Dec 8 08:02:46 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 8920C37B401 for ; Fri, 8 Dec 2000 08:02:45 -0800 (PST) Received: (qmail 24071 invoked by uid 1000); 8 Dec 2000 16:02:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 Dec 2000 16:02:44 -0000 Date: Fri, 8 Dec 2000 10:02:44 -0600 (CST) From: Mike Silbersack To: "Chad R. Larson" Cc: mjacob@feral.com, gallatin@cs.duke.edu, ken@kdm.org, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: PCIOCGETCONF/PCIOCREAD requires write permission? In-Reply-To: <200012080707.AAA12102@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message