From: Jan Niehusmann <jan@gondor.com>
To: linux-sound@vger.kernel.org
Subject: Re: C-Media 8x38 driver for kernel 2.4
Date: Mon, 05 Jun 2000 08:50:20 +0000 [thread overview]
Message-ID: <marc-linux-sound-96019700502935@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-96019100230870@msgid-missing>
On Mon, Jun 05, 2000 at 04:21:33AM -0400, Chen-Li Tien wrote:
> I also made a version that support kernel 2.2 and 2.4 (thanks for your
> work), and fixes since the version 3.21. I read that you add S/PDIF in/out
> in the init-module. May I remind you that they are not supported with all
> format, so if you only use 44k/48k then it is ok.
Is there any documentation about that topic available? I only found some
register descriptions, and used them (with some trial and error) to
enable s/pdif in and out. It's clearly an experimental feature.
It should not be a big problem to enable s/pdif only if compatible parameters
are used, with documentation available.
But I do have problems with lost or modified data - for testing purposes
I connected s/pdif out back to in, and piped a textfile through it (turn
your stereo off before you try this ;-) )
Some months ago I did an interesting observation: Corruptions were worse on
an idle system! As soon as I started to play music on a second sound card,
I saw nearly no lost bytes any more.
I'd really like to hear if other people have similar problems. Perhaps I just
got a bad sound card?
Jan
next prev parent reply other threads:[~2000-06-05 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-05 7:36 C-Media 8x38 driver for kernel 2.4 Paolo Rossi
2000-06-05 8:21 ` Chen-Li Tien
2000-06-05 8:40 ` Paolo Rossi
2000-06-05 8:50 ` Jan Niehusmann [this message]
2000-06-05 13:06 ` Chen-Li Tien
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=marc-linux-sound-96019700502935@msgid-missing \
--to=jan@gondor.com \
--cc=linux-sound@vger.kernel.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 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.