From owner-freebsd-current Sun Jun 25 15:20:22 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA10137 for current-outgoing; Sun, 25 Jun 1995 15:20:22 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA10130 for ; Sun, 25 Jun 1995 15:20:17 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id IAA08228; Mon, 26 Jun 1995 08:16:30 +1000 Date: Mon, 26 Jun 1995 08:16:30 +1000 From: Bruce Evans Message-Id: <199506252216.IAA08228@godzilla.zeta.org.au> To: peter@haywire.dialix.com Subject: Re: i386/563: isa conflict detection cannot handle ioaddr 0x0 Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk >The conflict detection code does not allow for the possibility that >a device does not have an IO address. 0 is a valid io address. I think the bug is actually that config generates address 0 instead of an out of bounds address for devices that don't have an io address. The out of bounds address should probably be -2. -1 is used for address `?'. However, Config fails to distinguish between `?' and `none' for other items, and isa.c only knows that -1 is special, so the out of bounds address should be -1 for now. Bruce