mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Thorpe <wd.dev@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: via8235 Audio on 2.4.21-pre
Date: Thu, 13 Feb 2003 22:18:02 +1100	[thread overview]
Message-ID: <20030213221802.09cd1afb.wd.dev@verizon.net> (raw)

Greetings,

For the past two months, I've been testing Alan's updates to the
via82cxxx_audio driver which allow the codecs attached to the VT8235 to
work quite nicely. Recent updates have allowed the majority of
applications to work, however any version of ESD fails (whilst the same
configuration works fine with other sound drivers). 

This has been a problem ever since the first via82cxxx_audio releases with
vt8235 support, but at present, I'm using 2.4.21-pre4-ac4. When ESD is
loaded, 3 of the five beeps are heard (unless the beeps are disabled, in
which I can get about 0.25 seconds of audio to play through ESound) and
then ESound will hang. Once esound is killed, I get the message:

via_audio: ignoring drain playback error -512

This has been tested on several motherboards with different codecs - most
of which generally work well when using normal OSS applications. However,
the VT1612A (Subsystem: VIA Technologies, Inc.: Unknown device 4161) which
has a PCM2 volume control which behaves as the Master volume should; on
this chip, the Master volume doesn't do anything at all.

Are there any debugging modes that I can activate on this driver to
provide more valuable information? I'd really like to see this chip
working as ALSA has had less success than the OSS driver with a few codecs
attached to the VT8235.

Thanks,
Jonathan

             reply	other threads:[~2003-02-13 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 11:18 Jonathan Thorpe [this message]
2003-02-13 20:40 ` Alan Cox

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=20030213221802.09cd1afb.wd.dev@verizon.net \
    --to=wd.dev@verizon.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®