From owner-freebsd-hackers  Thu Oct 12 10:48:48 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id KAA23320
          for hackers-outgoing; Thu, 12 Oct 1995 10:48:48 -0700
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA23314
          for <hackers@FreeBSD.ORG>; Thu, 12 Oct 1995 10:48:45 -0700
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA15445; Thu, 12 Oct 1995 10:44:12 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199510121744.KAA15445@phaeton.artisoft.com>
Subject: Re: I/O port 0 == autoconfig?
To: uhclem%nemesis@fw.ast.com (Frank Durda IV)
Date: Thu, 12 Oct 1995 10:44:11 -0700 (MST)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <m0t3Nqa-000IuWC@nemesis.lonestar.org> from "Frank Durda IV" at Oct 12, 95 08:38: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: 720       
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

> 	Change "visual" to treat "0" as an autoconfiguring I/O port
> 	parameter (can't be done for DMA or IRQs since 0 is legal for both)
> 
> 	Change the matcd driver and any other drivers doing similar
> 	things to use "0" as the key for autoconfiguring the I/O port
> 	it uses.

Can you use -2 instead?  And define manifest constants for them?

There exists DMA hardware that does not use DMA 0 internally, for which
it would be an allowable address.  Admittedly, this is mostly non-Intel
hardware, but the design shouldn't be so restrictive as to not allow
for non-Intel hardware.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.