From: Takashi Iwai <tiwai@suse.de>
To: Arve Knudsen <aknuds-1@broadpark.no>
Cc: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: nForce2 (intel8x0) playback doesn't accept 44khz
Date: Wed, 14 Jan 2004 13:09:05 +0100 [thread overview]
Message-ID: <s5heku268bi.wl@alsa2.suse.de> (raw)
In-Reply-To: <opr1rj39qxq1sf88@mail.broadpark.no>
At Wed, 14 Jan 2004 12:41:59 +0100,
Arve Knudsen wrote:
>
> Hello
>
> Has the intel8x0 driver been made accept only 48khz for playback? I always
> used 44.1, and wouldn't mind continuing to do so. Also, it really baffled
> me at first that it would accept 44.1 for capture, but not playback. Would
> someone care to explain, if this is how its meant to work?
it depends on ac97 codec. if the codec chip accepts the other rates,
the intel8x0 driver accepts them, too.
but for debugging, i need to know more basic info such as the version
you're using, which codec chips, which program doesn't work, etc...
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
next prev parent reply other threads:[~2004-01-14 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 11:41 nForce2 (intel8x0) playback doesn't accept 44khz Arve Knudsen
2004-01-14 12:09 ` Takashi Iwai [this message]
2004-01-14 12:27 ` Arve Knudsen
2004-01-14 13:43 ` Takashi Iwai
2004-01-14 13:57 ` Arve Knudsen
2004-01-14 14:02 ` Takashi Iwai
2004-01-14 14:12 ` Arve Knudsen
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=s5heku268bi.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=aknuds-1@broadpark.no \
--cc=alsa-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.