From: Nathan Bryant <nbryant@allegientsystems.com>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Thomas Gschwind <tom@infosys.tuwien.ac.at>, linux-kernel@vger.kernel.org
Subject: Re: [Fwd: i810_audio]
Date: Thu, 03 Jan 2002 14:39:06 -0500 [thread overview]
Message-ID: <3C34B35A.7000309@allegientsystems.com> (raw)
In-Reply-To: <3C3382CA.3000503@allegientsystems.com> <3C345493.5040800@evision-ventures.com> <20020103154718.C32419@infosys.tuwien.ac.at> <3C347A12.3070404@evision-ventures.com>
Martin Dalecki wrote:
[snip]
> example. The artsd from KDE as usuall is failing blatantly and locks
> the system hard...
> And I don't have neither the time, nor inclination for debuggin it...
> (Unless I could compile the whole KDE proerply with some recent
> gcc-3.x for RedHat ;-).
There were numerous problems in the 0.04 i810_audio driver that caused
problems with artsd. It sounds as if Tom has at least partial fixes for
most of these in his patch, but he doesn't mention the poll() problem
that we encountered...
artsd should work with 0.13 if we can get the SiS changes merged in. The
artsd problems weren't specific to the type of hardware changes Tom is
reporting... more like generic problems with the driver's
userland-interface semantics and DMA state tracking.
> Recodring did lockup the system hard as well immediately, no matter what.
Recording is something I never really tested heavily, though it does
seem to work at least minimally on my system (driver-default rates,
etc.) I'd be interested in any feedback as to whether it works in 0.13,
both from SiS users and otherwise...
Other people have said that RealProducer works fine, though, with newer
versions of Doug's driver, at all rates, etc.
next prev parent reply other threads:[~2002-01-03 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 21:59 [Fwd: i810_audio] Nathan Bryant
2002-01-03 12:54 ` Martin Dalecki
2002-01-03 14:47 ` Thomas Gschwind
2002-01-03 15:34 ` Martin Dalecki
2002-01-03 19:39 ` Nathan Bryant [this message]
2002-01-03 22:33 ` Nick Papadonis
2002-01-04 0:37 ` Nathan Bryant
2002-01-04 4:59 ` Doug Ledford
2002-01-04 5:09 ` Nathan Bryant
2002-01-04 5:31 ` Ben Clifford
2002-01-04 15:39 ` Doug Ledford
2002-01-04 19:37 ` Ben Clifford
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=3C34B35A.7000309@allegientsystems.com \
--to=nbryant@allegientsystems.com \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom@infosys.tuwien.ac.at \
/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