From: Lee Revell <rlrevell@joe-job.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: Takashi Iwai <tiwai@suse.de>, Emmanuel Fleury <fleury@cs.aau.dk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Re: [Alsa drivers] Creatives X-Fi chip
Date: Mon, 22 Aug 2005 17:54:55 -0400 [thread overview]
Message-ID: <1124747695.16064.46.camel@mindpipe> (raw)
In-Reply-To: <430A37B5.9050300@superbug.co.uk>
On Mon, 2005-08-22 at 21:38 +0100, James Courtier-Dutton wrote:
> We are not going to get any support from Creative for the X-Fi chip.
> We do not get support from Creative for any Creative chip that has a
> DSP in it.
Well, except for the emu10k1 driver that Creative wrote and released
years ago. I don't see why they can't do something similar with the
X-Fi stuff. We don't need or expect the DSP programming docs, just the
minimum to get sound in and out of the thing.
So do you expect Creative to leave thousands of emu10k1/emu10k2 Linux
users with no upgrade path? I think if they tried to do this we could
make it a real PR nightmare for them.
Lee
next prev parent reply other threads:[~2005-08-22 21:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 9:55 [Alsa drivers] Creatives X-Fi chip Emmanuel Fleury
2005-08-19 22:52 ` Lee Revell
2005-08-20 5:17 ` Lee Revell
2005-08-20 6:48 ` Emmanuel Fleury
2005-08-20 7:08 ` Lee Revell
2005-08-20 7:08 ` Lee Revell
2005-08-22 12:18 ` Takashi Iwai
2005-08-22 12:18 ` [Alsa-devel] " Takashi Iwai
2005-08-22 20:38 ` James Courtier-Dutton
2005-08-22 20:38 ` [Alsa-devel] " James Courtier-Dutton
2005-08-22 21:54 ` Lee Revell [this message]
2005-08-23 20:41 ` Peter Zubaj
2005-08-23 18:48 ` Lennart Sorensen
2005-08-23 18:48 ` [Alsa-devel] " Lennart Sorensen
2005-08-23 22:12 ` Lee Revell
2005-08-23 21:39 ` Lee Revell
2005-08-23 21:39 ` [Alsa-devel] " Lee Revell
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=1124747695.16064.46.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=fleury@cs.aau.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.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 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.