All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Nathan Bryant <nbryant@optonline.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i810 audio, problems with both GPL and 4Front driver
Date: Fri, 30 Nov 2001 22:01:23 -0500	[thread overview]
Message-ID: <3C084803.9090507@redhat.com> (raw)
In-Reply-To: <3C083424.7090309@optonline.net>

Nathan Bryant wrote:

> 
> FYI,
> 
> On my machine, the changes in 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=100651447318071&w=2 or 
> 2.4.17-pre1 don't fix the KDE problems, as alleged. artsd still exits 
> after consuming too much CPU. I've tried reducing fragment size to 512 
> with no effect.
> 
> If it makes any difference to the driver, the kernel is running with 
> APIC's and ACPI enabled on a uniprocessor build (Wow, acronym soup. ;)
> 
> for what it's worth, 4Front's binary driver (3.9.5, 3.9.6) has problems 
> too on this machine. KDE works but there are audio pops/speedups/stops. 
> (xmms, in particular, likes to stop for a while, then resume, sometimes 
> after a speedup.)


Just because I've been hearing about this stuff forever and the powers 
that be didn't take my i810_audio.c driver version 0.05 for some reason, 
I've place my 0.05 i810_audio.c file on my web site for anyone 
interested in testing it to see how it does.

http://people.redhat.com/dledford/i810_audio.c.gz





-- 

  Doug Ledford <dledford@redhat.com>  http://people.redhat.com/dledford
       Please check my web site for aic7xxx updates/answers before
                       e-mailing me about problems


      reply	other threads:[~2001-12-01  3:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01  1:36 i810 audio, problems with both GPL and 4Front driver Nathan Bryant
2001-12-01  3:01 ` Doug Ledford [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=3C084803.9090507@redhat.com \
    --to=dledford@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbryant@optonline.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.