From owner-freebsd-questions  Wed Oct 18 16:28:51 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id QAA01439
          for questions-outgoing; Wed, 18 Oct 1995 16:28:51 -0700
Received: from MediaCity.com (root@easy1.mediacity.com [205.216.172.10])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA01434
          for <freebsd-questions@freebsd.org>; Wed, 18 Oct 1995 16:28:46 -0700
Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id QAA15793; Wed, 18 Oct 1995 16:31:22 -0700
From: Brian Litzinger <brian@MediaCity.com>
Message-Id: <199510182331.QAA15793@MediaCity.com>
Subject: Re: cyb driver (port 0x0 problem)
To: KWWANG@CSUPomona.Edu (Kuo Wei)
Date: Wed, 18 Oct 1995 16:31:21 -0700 (PDT)
Cc: freebsd-questions@freebsd.org
In-Reply-To: <01HWLA1PEAGOASC7O3@clstac.is.csupomona.edu> from "Kuo Wei" at Oct 18, 95 03:44:50 pm
X-Mailer: ELM [version 2.4 PL24 ME8a]
Content-Type: text
Content-Length: 1131      
Sender: owner-questions@freebsd.org
Precedence: bulk

> 
> Hi there, it is me again :(
> 
> 	Well, I got the driver to compile+install (my fault for mis-read 1
> line in the install file), but now I'm having some problem getting the 2nd
> Cyclades recognize under FreeBSD.  Here's the output from kernel boot-up
> 
> -----
> cy returned 46
> cy returned 46
> cy returned 46
> cy returned 46
> cyb0 at 0x0 IRQ 10 maddr 0xd4000 msize 8192 on isa
> cyb1 not probed due to I/O address conflict with cyb0 at 0x0
> -----
>  

The problem is that the Cyclades board does not use any I/O ports.
so apparently the FreeBSD stuff defaults to a port of 0 for each
card, and hence the conflict.

I asked the "knowledgable_ones@freebsd" what to do about this and
never received an answer.

I can think of two possible solutions:

    1. to each driver entry add a 'port 0xXXX', where XXX is some
       unused location. XXX should be different for each cyb entry.

    2. depending on your rev of FreeBSD either

	 add 'option ALLOW_IO_CONFLICTS' to your kernel conf.

	 or add

         cyb1 port 0 conflict ...

	 to your kernel conf.

--
Brian Litzinger
brian@mediacity.com
http://www.mpress.com