From owner-freebsd-current Mon Jan 8 01:42:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA25698 for current-outgoing; Mon, 8 Jan 1996 01:42:47 -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 BAA25689 for ; Mon, 8 Jan 1996 01:42:40 -0800 (PST) Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id BAA00219; Mon, 8 Jan 1996 01:42:21 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.7.3/8.6.5) with SMTP id BAA01488; Mon, 8 Jan 1996 01:42:22 -0800 (PST) Message-Id: <199601080942.BAA01488@corbin.Root.COM> To: Michael Smith cc: james@else.net (James FitzGibbon), current@freebsd.org Subject: Re: Disposition of unknown PCI ethernet solved In-reply-to: Your message of "Mon, 08 Jan 96 19:30:51 +1030." <199601080900.TAA01821@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 08 Jan 1996 01:42:20 -0800 Sender: owner-current@freebsd.org Precedence: bulk >James FitzGibbon stands accused of saying: > >> 2. The visual kernel configuration program caused be half the problems >> with this card because it limits iobase entries for the ed0? device to no >> more than 0x2000. Using the command-line config program, it can be set >> higher. > >The visual config editor was not designed with PCI devices in mind, as >they were supposed to be automatically probed. 0x2000 is (AFAIK) the >highest legitimate address to which one would want to set an ISA or >ISA-like device to. > >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. -DG David Greenman Core Team/Principal Architect, The FreeBSD Project