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: [EMAIL PROTECTED]
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
