From owner-freebsd-current  Sun Jun  1 12:18:46 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id MAA01523
          for current-outgoing; Sun, 1 Jun 1997 12:18:46 -0700 (PDT)
Received: from nagual.pp.ru (ache.relcom.ru [194.58.229.133])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01516;
          Sun, 1 Jun 1997 12:18:34 -0700 (PDT)
Received: (from ache@localhost)
	by nagual.pp.ru (8.8.5/8.8.5) id XAA06504;
	Sun, 1 Jun 1997 23:19:18 +0400 (MSD)
Date: Sun, 1 Jun 1997 23:19:14 +0400 (MSD)
From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru>
To: Bruce Evans <bde@zeta.org.au>
cc: current@FreeBSD.ORG, se@FreeBSD.ORG
Subject: Re: Shared irq's broke sounddriver badly
In-Reply-To: <199706011858.EAA30970@godzilla.zeta.org.au>
Message-ID: <Pine.BSF.3.96.970601231625.6500A-100000@nagual.pp.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 2 Jun 1997, Bruce Evans wrote:

> >What I always have worked in my kernel configure:
> >
> >controller	snd0
> >device sb0      at isa? port 0x220 irq 5 drq 1 vector sbintr
> >device sbxvi0   at isa? port? irq? drq 5 conflicts
> >device opl0     at isa? port 0x388
> >device sbmidi0  at isa? port 0x330 irq? conflicts
> >
> >What I got now with new shared interrupts code:
> >
> >sb0 at 0x220-0x22f irq 5 drq 1 on isa
> >sb0: <SoundBlaster 16 4.16>
> >sbxvi0 at 0x220-0x22f irq 5 drq 5 on isa
> >sbxvi0: <SoundBlaster 16 4.16>
> >	device combination doesn't support shared irq5
> >	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >	intr_connect(irq5) failed, result=-1
> 
> This is not a new error.  intr_connect() just reports the error.
> config_isadev_c() ignores errors from register_intr().  I get this for
> all my ISA devices because I register the interrupts earlier without
> telling config_isadev_c().

Hmm. I just care about resolving this issue than about where this error
belongs too. If you know such deep details, could you please fix it
somehow?

> >opl0 at 0x388-0x38b irq 31 on isa
> >		    ^^^^^^		
> 
> What was it originally?

There is no IRQ for this device at all (according to config line).

-- 
Andrey A. Chernov
<ache@null.net>
http://www.nagual.pp.ru/~ache/