From: Brendan Pike <spike@spykes.net>
To: Chris Rankin <rankincj@yahoo.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: How much of the X-Fi (emu20k1) chip has Creative documented?
Date: Sun, 24 Jan 2010 09:26:55 -0500 [thread overview]
Message-ID: <20100124092655.18d6a92c@darius> (raw)
In-Reply-To: <s5h7hr7bxvm.wl%tiwai@suse.de>
On Sun, 24 Jan 2010 11:28:13 +0100
Takashi Iwai <tiwai@suse.de> wrote:
> At Sat, 23 Jan 2010 14:46:37 -0800 (PST),
> Chris Rankin wrote:
> >
> > --- On Sat, 23/1/10, Brendan Pike <spike@spykes.net> wrote:
> > > I'm 100% sure that HwMix is supported. When I said direct
> > > hardware access I meant it. I'm sure anyone else with an XFi card
> > > can confirm this too.
> >
> > That's just it - someone on Phoronix is saying that it isn't supported:
> > http://www.phoronix.com/forums/showthread.php?t=21486
> >
> > "Just as a FYI multi voice hardware mixing is not present in the linux x-fi drivers."
> >
> > That post is dated 17th Jan 2010.
>
> It's a wrong information.
>
>
> Takashi
X-Fi is such a generic term these days with Creative.
There are non emu20k1/2 based X-Fi's that do NOT support HWMix.
The Phoronix post was probably referring to those cards and thinking
it applies to all of them as a result.
Just a peek in the source code would show you that the hardware SRC is
supported.
next prev parent reply other threads:[~2010-01-24 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 0:43 How much of the X-Fi (emu20k1) chip has Creative documented? Chris Rankin
2010-01-18 20:51 ` Brendan Pike
2010-01-18 22:21 ` Chris Rankin
2010-01-18 22:27 ` Brendan Pike
2010-01-23 22:04 ` Chris Rankin
2010-01-23 22:41 ` Brendan Pike
2010-01-23 22:46 ` Chris Rankin
2010-01-24 10:28 ` Takashi Iwai
2010-01-24 14:26 ` Brendan Pike [this message]
2010-01-24 16:57 ` Chris Rankin
2010-01-25 6:57 ` Takashi Iwai
2010-01-25 8:49 ` Chris Rankin
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=20100124092655.18d6a92c@darius \
--to=spike@spykes.net \
--cc=alsa-devel@alsa-project.org \
--cc=rankincj@yahoo.com \
/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.