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: Mon, 18 Jan 2010 17:27:18 -0500 [thread overview]
Message-ID: <20100118172718.07c1053f@darius> (raw)
In-Reply-To: <506940.60549.qm@web52907.mail.re2.yahoo.com>
On Mon, 18 Jan 2010 14:21:57 -0800 (PST)
Chris Rankin <rankincj@yahoo.com> wrote:
> --- On Mon, 18/1/10, Brendan Pike <spike@spykes.net> wrote:
> > The matrix is horribly out of date. Yes PCIe cards
> > (emu20k2) are supported. HWMix also exists and works perfectly,
> That's interesting! Can you post the output of
>
> /proc/asound/<X-Fi card>/pcm0p/info
>
> please?
That doesn't exist here. The driver is limited in that it doesn't really
provide any information in /proc/asound at all.
>
> > I use an Auzentech X-Fi Forte myself, which works great.
>
> Are the emu20k1 cards equally well supported? It looks like emu20k2 cards are exclusively PCIe, whereas I'd probably be looking for a PCI card.
My previous card was a PCI emu20k1 based X-Fi Prelude, which worked the
same way as my current card does.
>
> Thanks,
> Chris
>
>
>
next prev parent reply other threads:[~2010-01-18 22:27 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 [this message]
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
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=20100118172718.07c1053f@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.