From owner-freebsd-current Thu Sep 7 13:29:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA07489 for current-outgoing; Thu, 7 Sep 1995 13:29:25 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA07475 for ; Thu, 7 Sep 1995 13:29:22 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.12/8.6.12) id NAA00639; Thu, 7 Sep 1995 13:28:42 -0700 From: "Rodney W. Grimes" Message-Id: <199509072028.NAA00639@gndrsh.aac.dev.com> Subject: Re: Getting around conflicts for a driver w/out base address To: pete@puffin.pelican.com (Pete Carah) Date: Thu, 7 Sep 1995 13:28:42 -0700 (PDT) Cc: current@freebsd.org In-Reply-To: from "Pete Carah" at Sep 7, 95 10:23:00 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 818 Sender: current-owner@freebsd.org Precedence: bulk > > In article <199509040622.QAA10078@godzilla.zeta.org.au> you write: > ... > >id_alive is the driver-alive flag corrupted to hold the i/o size. It isn't > >possible to set it at config time. Actually, we need a list of i/o port > >ranges because some drivers use scattered ports. > > Like the S3 chips that step on COM4? Talk about gratuitous conflicts... Though I agree that this is a rather nasty situation, the problem is not due to S3, it is casued by IBM's VGA register specifaction :-(. No one but no one ever uses those darn registers and I wish S3 would drop them, but that would voliate the compliance of the board to an official IBM spec :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD