From owner-freebsd-hackers Tue Nov 28 05:09:59 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA04342 for hackers-outgoing; Tue, 28 Nov 1995 05:09:59 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA04333 for ; Tue, 28 Nov 1995 05:09:53 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA30172; Wed, 29 Nov 1995 00:06:57 +1100 Date: Wed, 29 Nov 1995 00:06:57 +1100 From: Bruce Evans Message-Id: <199511281306.AAA30172@godzilla.zeta.org.au> To: bde@zeta.org.au, dawes@rf900.physics.usyd.edu.au Subject: Re: Problem with sio probe and Mach64 PCI video card Cc: hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG Precedence: bulk >>The change at the end replaces bogus internal array of ports by the ones >>specified in the config. This requires the config to specify sio2 and >>sio3 if the ports exist even if they are unusable under FreeBSD due to >>a conflict, and S3 owners to boot with -c and disable sio3 before the >>monitor blows up :-). sio3 shouldn't be in GENERIC. >The patch fixes the problem -- thanks! I don't understand why this means >that the config must specify ports that are not usable under FreeBSD. >I think "S3 owners" should be replaced by "IBM8514/A, S3, Mach{8,32,64} >and any chipset with an 8514/A ancestory owners". Com ports can get in each others way if they share an interrupt. There is only a problem after soft boots when the previous OS had interrupts enabled, but this problem is very confusing to debug and easy to fix if the ports are known - just initialize them all before attempting to use any. Bruce