From owner-freebsd-current Sat Apr 17 6:56:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-185-206.res.iastate.edu (friley-185-206.res.iastate.edu [129.186.185.206]) by hub.freebsd.org (Postfix) with ESMTP id 27F2C14EBB for ; Sat, 17 Apr 1999 06:56:27 -0700 (PDT) (envelope-from cc@137.org) Received: from friley-185-205.res.iastate.edu (friley-185-205.res.iastate.edu [129.186.185.205]) by friley-185-206.res.iastate.edu (Postfix) with ESMTP id 4F5BCA6; Sat, 17 Apr 1999 07:53:46 -0600 (CST) Received: from friley-185-205.res.iastate.edu (localhost [127.0.0.1]) by friley-185-205.res.iastate.edu (Postfix) with ESMTP id D47DBAC; Sat, 17 Apr 1999 08:53:45 -0500 (CDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm Cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-reply-to: Your message of "Sat, 17 Apr 1999 15:25:56 +0800." <19990417072558.578211F69@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 17 Apr 1999 08:53:45 -0500 From: Chris Csanady Message-Id: <19990417135345.D47DBAC@friley-185-205.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Chris Piazza wrote: >> On 17-Apr-99 Brian Feldman wrote: >> > Both sound drivers are broken with the new-bus code. My SB16, in the old >> > driver, now gets recognized but sbxvi is never looked for. pcm0, the new >> > 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: 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.. > >This is an ESS clone card: > >Probing for PnP devices: >CSN 1 Vendor ID: ESS1868 [0x68187316] Serial 0xffffffff Comp ID: PNPb02f [0x2f b0 >d041] >ESS1868 (rev 11) >pcm1 (ESS1868 sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 on isa > >This is an on-board Crystal SB-like PnP device: > >Probing for PnP devices: >CSN 1 Vendor ID: CSC0b36 [0x360b630e] Serial 0xffffffff Comp ID: @@@0000 [0x00 00 >0000] >mss_attach 1 at 0x530 irq 5 dma 1:0 flags 0x10 >pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 5 drq 1 fl >ags 0x10 on isa > >For what it's worth, PnP has for the most part not been changed under >new-bus and is using the old mechanisms. The only significant risk is that >the attach code doesn't like what I've done with the emulation of >isa_device->id_id for "unit numbers". I thought PnP was not even using new-bus yet?! I haven't used PnP in a long time, but the pcm driver is broke for me too. I have used the following successfully with just the plain isa0 for quite some time.. device pcm0 at isa? port? tty irq 5 drq 1 flags 0x10 >I'm sorry, you're going to need to have a bit of a look around and turning >on or inserting some debug code to see what's happening. Where should I start? It doesn't print out anything upon boot.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message