From owner-freebsd-current  Tue May 20 21:32:00 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA17092
          for current-outgoing; Tue, 20 May 1997 21:32:00 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA17086;
          Tue, 20 May 1997 21:31:52 -0700 (PDT)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 1.60 #1)
	id 0wU33f-0006Cf-00; Tue, 20 May 1997 22:31:27 -0600
To: Michael Smith <msmith@atrad.adelaide.edu.au>
Subject: Re: Backwards compatibiliy for isa_driver 
Cc: dfr@nlsystems.com (Doug Rabson), se@freebsd.org, current@freebsd.org
In-reply-to: Your message of "Tue, 20 May 1997 22:47:07 +0930."
		<199705201317.WAA02812@genesis.atrad.adelaide.edu.au> 
References: <199705201317.WAA02812@genesis.atrad.adelaide.edu.au>  
Date: Tue, 20 May 1997 22:31:27 -0600
From: Warner Losh <imp@village.org>
Message-Id: <E0wU33f-0006Cf-00@rover.village.org>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199705201317.WAA02812@genesis.atrad.adelaide.edu.au> Michael Smith writes:
: It means that "ISA" instances of a device can only be expected in the
: range 0x100-0x400, but that if the motherboard chipset is broken or
: old, probes at higher multiples of the device's address may still show
: it up.  This is not normally a problem, as you only go above there for
: EISA/PCI devices.

I know that my 8-bit serial cards show up at the same address that my
16bit S3 uses, so I can't have a cua3 on this machine....  The 8bit
card doesn't have the address lines to decode things any other way...

Warner