Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Apr 1999 01:36:01 +0800
From:      Peter Wemm <peter@netplex.com.au>
To:        Brian Feldman <green@unixhelp.org>
Cc:        current@FreeBSD.ORG
Subject:   Re: new-bus breaks both sound drivers 
Message-ID:  <19990417173603.95D531F58@spinner.netplex.com.au>
In-Reply-To: Your message of "Sat, 17 Apr 1999 13:15:29 -0400." <Pine.BSF.4.10.9904171313050.21249-100000@janus.syracuse.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
Brian Feldman wrote:
> On Sat, 17 Apr 1999, Peter Wemm wrote:
> > Chris Piazza wrote:
> > > On 17-Apr-99 Brian Feldman wrote:
> > > > Both sound drivers are broken with the new-bus code. My SB16, in the ol
    d
> > > > driver, now gets recognized but sbxvi is never looked for. pcm0, the ne
    w
> > > > driver, never initializes with the new code :(
> > > > 
> > > > device pcm0 at isa? port? tty irq 5 drq 1 flags 0x16
> > > > 
> > > 
> > > The pcm0 sounddriver works for me.  In fact, the only problem I had with 
    new
> > > bus was it is now pcm0 instead of pcm1 ;-).
> > > 
> > > es0: <AudioPCI ES1370> at device 9.0 on pci0
> > > pcm0: using I/O space register mapping at 0xd800
> > > es0: interrupting at irq 4
> > > 
> > > device          pcm0
> > 
> > On two different systems it works for me using pcm0..

> Here's what's going on with the pcm code. I've got an on-board audio device
> that should probably eventually be supported, is PnP and detected, but
> not recognized by the pcm driver. However, my SB16 ALSO fails to be attached.
> My SB16 is a nice pre-PnP one, which used to work fine with either audio
> driver. I'll paste my current config and dmesg.

[..]
> # Luigi's snd code.
> # You may also wish to enable the pnp controller with this, for pnp
> # sound cards.
> #
> device pcm0
> device pcm1 at isa? port? tty irq 5 drq 1 flags 0x16
[..]


Hmm, you might like to try this patch and see what happens, there is
a missing old driver wrapper for the pcm stuff.  As a result, it's not
getting run from the isa probe.  Regarding the other driver, I'm not
sure what's going on there as the hooks appear to be present.

Index: i386/isa/isa_compat.h
===================================================================
RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.h,v
retrieving revision 1.1
diff -u -r1.1 isa_compat.h
--- isa_compat.h	1999/04/16 21:22:23	1.1
+++ isa_compat.h	1999/04/17 17:30:34
@@ -49,6 +49,7 @@
 #include "ze.h"
 #include "zp.h"
 #include "oltr.h"
+#include "pcm.h"
 #include "pas.h"
 #include "sb.h"
 #include "sbxvi.h"
@@ -117,6 +118,7 @@
 extern struct isa_driver  zedriver;
 extern struct isa_driver  zpdriver;
 extern struct isa_driver oltrdriver;
+extern struct isa_driver pcmdriver;
 extern struct isa_driver pasdriver;
 extern struct isa_driver  sbdriver;
 extern struct isa_driver sbxvidriver;
@@ -320,6 +322,9 @@
 
 #if NOLTR > 0
 	{ DRIVER_TYPE_MISC, &oltrdriver },
+#endif
+#if NPCM > 0
+	{ DRIVER_TYPE_MISC, &pcmdriver },
 #endif
 #if NPAS > 0
 	{ DRIVER_TYPE_MISC, &pasdriver },


Cheers,
-Peter



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990417173603.95D531F58>