From owner-freebsd-current  Mon Jan  8 02:29:11 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA29221
          for current-outgoing; Mon, 8 Jan 1996 02:29:11 -0800 (PST)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA29215
          for <current@freebsd.org>; Mon, 8 Jan 1996 02:29:04 -0800 (PST)
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id CAA00330; Mon, 8 Jan 1996 02:29:02 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.7.3/8.6.5) with SMTP id CAA01549; Mon, 8 Jan 1996 02:29:03 -0800 (PST)
Message-Id: <199601081029.CAA01549@corbin.Root.COM>
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: james@else.net, current@freebsd.org
Subject: Re: Disposition of unknown PCI ethernet solved 
In-reply-to: Your message of "Mon, 08 Jan 96 20:18:51 +1030."
             <199601080948.UAA02007@genesis.atrad.adelaide.edu.au> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Mon, 08 Jan 1996 02:28:59 -0800
Sender: owner-current@freebsd.org
Precedence: bulk

>David Greenman stands accused of saying:
>> >If the PCI code (Stefan?) can't bend the ed driver around to talk to this 
>> >card, then obviously visuserconfig() should be updated 8)
>> 
>>    The 'ed' driver is an ISA device, not PCI. There is nothing special about
>> 0x2000 - ISA devices can use port addresses anywhere in the 16bit 0x0-0xffff
>> range.
>
>Hmm, then why did I pick it? 8)

   I was kinda hoping that you'd be able to tell me... :-)

>  I'm aware that 0x400 is the conventional
>hardware limit for 'true' ISA, and my recollection is that there were a few
>extra address line son EISA slots, but I'm obviously hazy on that one.

   Early ISA controllers only decode 10 bits worth. The convention for EISA
is slot # * 0x1000.

-DG

David Greenman
Core Team/Principal Architect, The FreeBSD Project