From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: intel8x0 has stopped working.
Date: Mon, 09 Feb 2004 11:56:56 +0100 [thread overview]
Message-ID: <s5hllnc7c7b.wl@alsa2.suse.de> (raw)
In-Reply-To: <4023F396.7030407@superbug.demon.co.uk>
At Fri, 06 Feb 2004 20:05:42 +0000,
James Courtier-Dutton wrote:
>
> Takashi Iwai wrote:
> > At Thu, 05 Feb 2004 22:28:03 +0000,
> > James Courtier-Dutton wrote:
> >
> >>I checked out a new anonymouse cvs of alsa-driver/alsa-kernel, applied
> >>your patch, and attach the output from doing modprobe snd-intel8x0.
> >>
> >>I can only see printf's in the patch, so I don't see how it could have
> >>fixes the VRA.
> >
> >
> > no, it doesn't fix yet.
> >
> >
> >>Feb 5 22:22:53 new kernel: determined VRA rates: 0xfe
> >>Feb 5 22:22:53 new kernel: determined VRA rates: 0xfe
> >>Feb 5 22:22:53 new kernel: determined SPDIF rates: 0xe0
> >>Feb 5 22:22:53 new kernel: determined SDAC rates: 0x80
> >>Feb 5 22:22:53 new kernel: determined LDAC rates: 0x80
> >
> >
> > here's the problem. surround and LFE DAC sample rates are not
> > detected properly.
> > i don't figure out yet why...
> >
> > does the attached patch have influence? check the messages above.
> > (it doesn't contain the patch to ac97_pcm.c. it's not needed now.)
> >
> >
> > Takashi
> >
> >
> I checked out a new cvs of alsa-driver, alsa-kernel
> Added your patch, and the rates are detected correctly now, and the
> rates change on the hardware correctly now.
> Thanks
thanks for the confirmation. i'll apply the patch to cvs.
> By looking at your code, it looks like you are making sure the rate for
> the Front, Surround and Center/LFE all change together, which seems to
> work, although, the alc650 datasheet spec does not seem to mention that
> this has to happen. Why have 3 ac97 registers, if they all have to
> change together?
we're fooled :)
sometime it is explicitly written that the surround and LFE rates are
simply the mirror of the front/center rate.
that's why the fix came into my mind.
Takashi
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
prev parent reply other threads:[~2004-02-09 11:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 17:41 intel8x0 has stopped working James Courtier-Dutton
2004-02-02 17:59 ` Takashi Iwai
2004-02-02 19:34 ` Prakash K. Cheemplavam
2004-02-02 19:42 ` James Courtier-Dutton
2004-02-02 23:12 ` [PATCH] Fixes: " James Courtier-Dutton
2004-02-03 16:22 ` Jaroslav Kysela
2004-02-03 22:21 ` James Courtier-Dutton
2004-02-05 11:01 ` Jaroslav Kysela
2004-02-05 19:15 ` Glenn Maynard
2004-02-05 19:25 ` Takashi Iwai
2004-02-05 19:38 ` Jaroslav Kysela
2004-02-05 19:58 ` Glenn Maynard
2004-02-05 20:44 ` James Courtier-Dutton
2004-02-04 19:35 ` Takashi Iwai
2004-02-04 23:03 ` James Courtier-Dutton
2004-02-05 18:49 ` Takashi Iwai
2004-02-05 19:42 ` Takashi Iwai
2004-02-05 22:28 ` James Courtier-Dutton
2004-02-06 11:29 ` Takashi Iwai
2004-02-06 20:05 ` James Courtier-Dutton
2004-02-09 10:56 ` Takashi Iwai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hllnc7c7b.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.demon.co.uk \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox