From nobody Sat Nov 30 11:52:02 1996 Received: (from nobody@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA04352; Sat, 30 Nov 1996 11:52:02 -0800 (PST) Message-Id: <199611301952.LAA04352@freefall.freebsd.org> Date: Sat, 30 Nov 1996 11:52:02 -0800 (PST) From: pgiffuni@fps.biblos.unal.edu.co To: freebsd-gnats-submit@freebsd.org Subject: Installation bug X-Send-Pr-Version: www-1.0 >Number: 2130 >Category: conf >Synopsis: Installation bug >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Nov 30 12:00:01 PST 1996 >Closed-Date: Sun Dec 8 21:13:47 PST 1996 >Last-Modified: Sun Dec 8 21:16:53 PST 1996 >Originator: Pedro Giffuni >Release: 2.2-Alpha >Organization: Universidad Nacional >Environment: >Description: No PCI support can be removed before installing the OS! >How-To-Repeat: Visual mode. >Fix: >Release-Note: >Audit-Trail: From: J Wunsch To: pgiffuni@fps.biblos.unal.edu.co Cc: freebsd-gnats-submit@freebsd.org Subject: Re: conf/2130: Installation bug Date: Sun, 1 Dec 1996 00:13:35 +2500 (MET) As pgiffuni@fps.biblos.unal.edu.co wrote: > >Description: > No PCI support can be removed before installing the OS! Well, it's not even _supposed_ to be removable. PCI devices are believed to be reliably auto-configurable. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From: se@freebsd.org (Stefan Esser) To: pgiffuni@fps.biblos.unal.edu.co Cc: freebsd-gnats-submit@freebsd.org Subject: Re: conf/2130: Installation bug Date: Sun, 1 Dec 1996 15:27:14 +0100 On Nov 30, pgiffuni@fps.biblos.unal.edu.co wrote: > > >Number: 2130 > >Category: conf > >Synopsis: Installation bug > >Description: > No PCI support can be removed before installing the OS! This is the way it is uspposed to be ... We could add a DISABLE function to the config code, which would directly write some bit in the PCI device's config space command register. This would completely deactivate the device (except for config space accesses) and the PCI code could respect this bit (while it currently tries hard to gat all devices activated that the PCI BIOS might have forgotten, for example behind a PCI to PCI bridge ...) I'm not sure there are really good applications for a ONE time dactivate of a PCI device. And the PCI code assumes that all devices are auto- configuring. And for that reason, a device might be found at a different address (and even in a different 'slot') on each reboot without violating the specs. (This will happen, if you add cards with PCI to PCI bridges and bus. Then, even the bus number of previously installed devices may come out differently ...) Regards, STefan From: "Pedro Giffuni S." To: Stefan Esser Cc: freebsd-gnats-submit@freebsd.org Subject: Re: conf/2130: Installation bug Date: Sun, 01 Dec 1996 11:30:01 -0800 Just add a small message (when someone presses enter) saying "Device will autodetect safely and cannot be removed". The end user doesn´t need to know the details of PCIs. Pedro. Stefan Esser wrote: > > On Nov 30, pgiffuni@fps.biblos.unal.edu.co wrote: > > > > >Number: 2130 > > >Category: conf > > >Synopsis: Installation bug > > >Description: > > No PCI support can be removed before installing the OS! > > This is the way it is uspposed to be ... > > > Regards, STefan State-Changed-From-To: open->closed State-Changed-By: msmith State-Changed-When: Sun Dec 8 21:13:47 PST 1996 State-Changed-Why: Message displayed by visual userconfig updated to indicate that PCI devices cannot be deleted/configured, hopefully reducing the possibiity of confusion. >Unformatted: