Date: Sun, 29 Sep 1996 11:03:41 -0700 (PDT) From: nsayer@quack.kfu.com To: FreeBSD-gnats-submit@freebsd.org Subject: kern/1690: apm and SB 16 conflict inappropriately. Message-ID: <199609291803.LAA06705@icarus.kfu.com> Resent-Message-ID: <199609291810.LAA20297@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 1690 >Category: kern >Synopsis: apm and sbxvi inappropriately probe as conflicting >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Sep 29 11:10:01 PDT 1996 >Last-Modified: >Originator: Nick Sayer >Organization: just me >Release: FreeBSD 2.2-960801-SNAP i386 >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. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609291803.LAA06705>