public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Sergei Haller <Sergei.Haller@math.uni-giessen.de>
Cc: whitney@math.berkeley.edu, LKML <linux-kernel@vger.kernel.org>
Subject: Re: via 686a audio driver rate locked at 48Khz
Date: Fri, 02 Mar 2001 08:31:22 -0500	[thread overview]
Message-ID: <3A9FA0AA.9E4A5CAB@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0103021419461.3806-100000@fb07-calculator.math.uni-giessen.de>

Sergei Haller wrote:
> 
> On Wed, 28 Feb 2001, Jeff Garzik wrote:
> 
> > Wayne Whitney wrote:
> > > I have a system with an MSI-6321 motherboard with the Via 686a
> > > southbridge, and I'm having a little trouble with the via82cxxx_audio
> > > sound driver.  The stock 2.4.2 driver produces only a rhythmic a buzzing
> > > sound.  I saw a patch here a week or two ago for 'rate locking', so I
> > > tried that (it didn't apply cleanly to 2.4.2, but I think I applied it by
> > > hand correctly).
> >
> > FYI I sent that change to Linus just now, and posted a quick update on
> > the Web site:  http://sourceforge.net/projects/gkernel/
> 
> with this 1.1.14b I still can't cat wav files to /dev/dsp but
> the aRts deamon (from kde2.0.1) works if I set it to 48000Hz

Unless the wav file is at 48000 Hz and you set the rate to 48000 Hz,
that's correct.  You'll need arts or esd or a sound app that supports
locked rates.

	Jeff


-- 
Jeff Garzik       | "You see, in this world there's two kinds of
Building 1024     |  people, my friend: Those with loaded guns
MandrakeSoft      |  and those who dig. You dig."  --Blondie

      reply	other threads:[~2001-03-02 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-28 18:31 via 686a audio driver rate locked at 48Khz Wayne Whitney
2001-02-28 23:19 ` Jeff Garzik
2001-03-02 13:25   ` Sergei Haller
2001-03-02 13:31     ` Jeff Garzik [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=3A9FA0AA.9E4A5CAB@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=Sergei.Haller@math.uni-giessen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=whitney@math.berkeley.edu \
    /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