From nsayer@quack.kfu.com  Sun Sep 29 11:03:46 1996
Received: from quack.kfu.com (quack.kfu.com [204.147.226.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15524
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 29 Sep 1996 11:03:44 -0700 (PDT)
Received: from icarus.kfu.com (icarus.kfu.com [204.147.226.3]) by quack.kfu.com (8.6.12/8.6.12) with ESMTP id LAA05259 for <FreeBSD-gnats-submit@freebsd.org>; Sun, 29 Sep 1996 11:03:42 -0700
Received: by icarus.kfu.com 
        (8.7.5//ident-1.0) id LAA06705; Sun, 29 Sep 1996 11:03:41 -0700 (PDT) 
Message-Id: <199609291803.LAA06705@icarus.kfu.com>
Date: Sun, 29 Sep 1996 11:03:41 -0700 (PDT)
From: nsayer@quack.kfu.com
Reply-To: nsayer@quack.kfu.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: apm and SB 16 conflict inappropriately.
X-Send-Pr-Version: 3.2

>Number:         1690
>Category:       kern
>Synopsis:       apm and sbxvi inappropriately probe as conflicting
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 29 11:10:01 PDT 1996
>Closed-Date:    Sat May 23 02:32:55 PDT 1998
>Last-Modified:  Sat May 23 02:33:07 PDT 1998
>Originator:     Nick Sayer
>Release:        FreeBSD 2.2-960801-SNAP i386
>Organization:
just me
>Environment:

controller      snd0
device          sb0     at isa? port 0x220 irq 5 drq 1 vector sbintr
device          sbxvi0  at isa? drq 5
device          sbmidi0 at isa? port 0x330
device          opl0    at isa? port 0x388

device          apm0    at isa?

>Description:

The code that detects conflicting driver configs complains needlessly
about config items that are "don't care".

>How-To-Repeat:

boot a kernel containing the above config.

apm0 will not be probed. It will be reported as conflicting with
sbxvi0.

>Fix:
	
The problem is that both apm0 and sbxvi0 end up with I/O address 0.
This doesn't matter, since neither uses the I/O address portion.

A workaround is to add 'conflicts' to the apm0 line, but a better fix
would be for the conflict detection code not to care about items which
appear to conflict but are 0.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Sat May 23 02:32:55 PDT 1998 
State-Changed-Why:  
I belive this is fixed. 
>Unformatted:
