Date: Tue, 1 Oct 1996 19:09:10 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: msmith@atrad.adelaide.edu.au, bde@freebsd.org, current@freebsd.org Subject: Re: Your UserConfig changes for unmasking PCI devices... Message-ID: <199610010939.TAA11012@genesis.atrad.adelaide.edu.au> In-Reply-To: <4208.844162454@time.cdrom.com> from "Jordan K. Hubbard" at Oct 1, 96 02:34:14 am
next in thread | previous in thread | raw e-mail | index | archive | help
Jordan K. Hubbard stands accused of saying: > > Even having the bus type displayed in the description string, perhaps > in a different text attribute, would be enough. So you'd see: > > bt0 Buslogic SCSI controller [PCI] > bt0 Buslogic SCSI controller [ISA/EISA/VLB] > > And *only* if the machine in question even had a PCI bus. I can't see > any reason to show the PCI entries on my 486/EISA test machine. :-) Problems : - "different text attributes" aren't (properly) supported by syscons at that point in the boot process. - how is userconfig supposed to know what hardware the system has? I thought the whole idea behind it was for it to run _before_ hardware had been located, not afterwards. I only planned to put PCI devices in as a calmative for users who might otherwise bitch about not being able to see them. It might make more sense just to rip them right out again. > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610010939.TAA11012>