From owner-freebsd-current Sat Apr 17 10:31: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 4B3EF15485 for ; Sat, 17 Apr 1999 10:30:57 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id NAA15165; Sat, 17 Apr 1999 13:26:18 -0400 (EDT) Date: Sat, 17 Apr 1999 13:26:18 -0400 (EDT) From: Chuck Robey To: Brian Feldman Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: new-bus breaks both sound drivers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Apr 1999, 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 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 [bunch of dmesg delete] [here from Peter] > > 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'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. > > 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. FWIW, using a 2 hour old kernel, my Turtle Beach Malibu PCI PnP card works just fine: [from my config file] device pcm0 at isa? port ? tty irq 15 drq 1 [from my dmesg] Probing for PnP devices: Trying Read_Port at 203 CSN 1 Vendor ID: CSC7537 [0x3775630e] Serial 0xffffffff Comp ID: @@@0000 [0x0000 0000] PnP: override config for CSN 1 LDN 0 vend_id 0x3775630e port 0x0000 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 0 Called nullpnp_probe with tag 0x00000001, type 0x3775630e port 0x0534 0x0000 0x0220 0x0000 irq 15:0 drq 1:0 en 1 port 0x0534 0x0000 0x0220 0x0000 irq 15:0 drq 1:0 en 1 mss_attach 1 at 0x530 irq 15 dma 1:0 flags 0x10 pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 15 drq 1 f lags 0x10 on isa Notice that the line beginning "port" shows twice, which is an odditity. I use a line in my kernel.conf of: pnp 1 0 os enable port0 0x534 port2 0x220 irq0 15 drq0 1 drq1 0 I'm not saying Brian doesn't have a real problem, but I *am* saying that not all PCI PnP sound is broken. > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message