Date: Mon, 06 Sep 1999 16:01:52 +0800 From: Peter Wemm <peter@netplex.com.au> To: Doug Rabson <dfr@nlsystems.com> Cc: David Scheidt <dscheidt@tumbolia.com>, freebsd-current@freebsd.org Subject: Re: another newpcm casualty Message-ID: <19990906080152.8F1771CAB@overcee.netplex.com.au> In-Reply-To: Your message of "Mon, 06 Sep 1999 08:55:39 %2B0100." <Pine.BSF.4.10.9909060855150.2081-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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)).
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?19990906080152.8F1771CAB>