From owner-freebsd-current  Sun Sep  3 06:17:35 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id GAA17404
          for current-outgoing; Sun, 3 Sep 1995 06:17:35 -0700
Received: from iworks.InterWorks.org (iworks.interworks.org [128.255.18.10])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id GAA17398
          for <freebsd-current@freebsd.org>; Sun, 3 Sep 1995 06:17:34 -0700
Received: by iworks.InterWorks.org
	(1.37.109.8/16.2) id AA26276; Sun, 3 Sep 1995 08:12:50 -0500
Message-Id: <9509031312.AA26276@iworks.InterWorks.org>
Date: Sun, 3 Sep 1995 08:12:50 -0500
From: "Daniel M. Eischen" <deischen@iworks.InterWorks.org>
To: freebsd-current@freebsd.org
Subject: Re: Getting around conflicts for a driver w/out base address
Sender: current-owner@freebsd.org
Precedence: bulk


>>>   /*
>>>    * Drivers that do not have IO base addresses should return this
>>>    * in the probe routine.
>>>    */
>>>   #define ISA_NO_IOBASE  -1
>>> 
>>> or something like that.  That way it becomes apparent what a driver should
>>> do.
>
>It would be better to fix the interface (introduce an id_iosize field ...).
>In in any case, it is more important to document the requirement to return
>the i/o size for i/o mapped devices.  Many old little-used drivers still
>do this wrong:

Isn't there already a size field - id_alive?  At least that's how it looks
like it is being used in isa.c.  It is set to the value returned by a driver's
probe function.

How about making the drivers set this field like they do for others (id_maddr
and id_msize for example)?  Then the probe routine can actually return a
success/fail status.

Or is it more complicated than this when considering config?

Dan Eischen
deischen@iworks.InterWorks.org