From owner-freebsd-current Mon Sep 6 1:24:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1966A159CA for ; Mon, 6 Sep 1999 01:24:52 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA29587; Mon, 6 Sep 1999 09:25:28 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 6 Sep 1999 09:25:28 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: David Scheidt , freebsd-current@freebsd.org Subject: Re: another newpcm casualty In-Reply-To: <19990906080152.8F1771CAB@overcee.netplex.com.au> 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 Mon, 6 Sep 1999, Peter Wemm wrote: > Doug Rabson wrote: > > On Sun, 5 Sep 1999, David Scheidt wrote: > > > > > On Sun, 5 Sep 1999, Doug Rabson wrote: > > > > > > > On Sun, 5 Sep 1999, David Scheidt wrote: > > > > > > > > > Yesterday's -current fails to find my soundcard. It's an Opti chipset > thing > > > > > that worked fine (for a $12 soundcard...) with the old driver. What is > > > > > decent soundcard that works with the new driver? pnpinfo and dmesg s > nippet > > > > > for the thing: > > > > > > > > Try this patch: > > > > > > The card is now found, but when I try to use it, I get hundreds and hundred > s > > > of messages like > > > Sep 5 19:09:33 tumbolia /kernel: AD_WAIT_INIT FAILED 201 0xff in > > > /var/log/messages followed by > > > Sep 5 19:09:33 tumbolia /kernel: mss: Auto calibration timed out(1). > > > > So the patch didn't change the behaviour at all? > > I vaguely remember something about MSS devices sometimes using 0x530 vs 0x534 > and sometimes putting the registers at offset 0 and sometimes at +4. (ie: > using a PnP base address of 0x534 and the registers at 0x534 (ie: +0) and > other times the PnP register window at 0x530 and the mss registers at 0x534 > (ie: +4)). We have a flag for that in the mss driver (BD_F_MSS_OFFSET) which the pnp part attempts to initalise based on the ID. I thought that was the problem in this case but it doesn't seem to have changed anything. Maybe my patch was wrong. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message