From: ultrapenguin@netscape.net (jeramy b smith)
To: iweiny@acm.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Creative SBLive card
Date: Sat, 05 May 2001 01:53:38 -0400 [thread overview]
Message-ID: <680004CB.2F3BD659.A41E0FAA@netscape.net> (raw)
In-Reply-To: 3AF05597.F7D0C433@acm.org
I had the chance to test the patches and here is the results:
http://penguinppc.org/~jeramy/sshot.jpg
The first caveat is that the Channel 1 just makes noise. I had to plug my speakers into Channel2. The second caveat it that I had to move the Line3 slider all the way to zero to. It acts like an inverse PCM almost.
So there may be a few endiness issues left with the main sound channel aka channel 1.
But hey, I like rigged emu10k1 better than dmasound already.
-jeramy b smith
--
-jeramy b smith
"Linux is Fun!" -Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-05-05 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 18:44 Creative SBLive card Ira Weiny
2001-05-02 8:53 ` jeramy b smith
2001-05-03 0:15 ` Tony Arnold
2001-05-05 5:53 ` jeramy b smith [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=680004CB.2F3BD659.A41E0FAA@netscape.net \
--to=ultrapenguin@netscape.net \
--cc=iweiny@acm.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).