From: Alex Deucher <adeucher@UU.NET>
To: rainer@konqui.de, linux-kernel@vger.kernel.org
Subject: Re: seti@home and es1371
Date: Wed, 31 Jan 2001 14:13:40 -0500 [thread overview]
Message-ID: <3A7863E4.C7323E96@uu.net> (raw)
Rainer,
I'm not too familiar with the ct5880 sound chip that comes built onto
motherboards. I do know that alot of the AC'97 compliant built in sound
chips tend to let the host cpu do most of the processing involved in
playing the sound. That being said, even if you have a dedicated sound
processor, mp3 decoding is very processor intensive. It just so happens
that seti is also very processor intensive. Both of these processes are
vying for time on the cpu. Since both of these processes are so
processor intensive and the cpu can only do one thing at a time, the
performance of one or the other process will suffer from time to time.
Alex
----------------------------------------
Hi,
I hope you can help me. I have a problem with my on board soundcard and
seti. I have a Gigabyte GA-7ZX Creative 5880 sound chip. I use the
kernel
driver es1371 and it works goot. But when I run seti@home I got some
noise
in my sound when I play mp3 and other sound. But it is not every time
10s
play good than for 2 s bad and than 10s good 2s bad and so on. When I
kill
seti@home every thing is ok. So what can I do?
I have a Athlon 800 Mhz and 128 MB RAM
cu
Rainer
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-31 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 19:13 Alex Deucher [this message]
2001-02-10 0:25 ` seti@home and es1371 Dr. Kelsey Hudson
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 16:11 Rainer Wiener
2001-01-31 19:28 ` LA Walsh
2001-02-01 9:13 ` Rainer Wiener
[not found] ` <3A792A49.CDE8FBE0@sgi.com>
2001-02-01 9:57 ` Rainer Wiener
2001-02-01 0:09 ` Joerg Dietrich
2001-02-01 6:40 ` Robert-Jan Oosterloo
2001-02-01 9:11 ` Rainer Wiener
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=3A7863E4.C7323E96@uu.net \
--to=adeucher@uu.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rainer@konqui.de \
/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