From: Lee Revell <rlrevell@joe-job.com>
To: Peter Zubaj <pzubaj@gaya.sk>
Cc: James Courtier-Dutton <James@superbug.co.uk>,
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: Tue, 23 Aug 2005 17:39:58 -0400 [thread overview]
Message-ID: <1124833199.30517.23.camel@mindpipe> (raw)
In-Reply-To: <1124829672.3351.5.camel@localhost.localdomain>
On Tue, 2005-08-23 at 21:41 +0100, Peter Zubaj wrote:
> This is too expensive card to be only able use it as simple card.
> My advice buy something else.
> I don't think fight with creative can bring anything good to linux.
> Leave Creative as is. There is plenty of other hardware from other
> manufacturer worth money.
I agree, but the fact is that the emu10k* devices own the Windows gamer
market and like it or not these devices will sell millions of units, and
they've worked perfectly in Linux for years. So these users have a
reasonable expectation that Creative will provide them an upgrade path,
just like they did for SBLive! -> Audigy1 and Audigy1 -> Audigy2.
I'm not trying to pick a fight with Creative, but regardless of what I
(or any Linux developer) does, there's going to be a fight if they try
to lock out Linux users.
Lee
prev parent reply other threads:[~2005-08-23 21:40 UTC|newest]
Thread overview: 12+ 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-22 12:18 ` [Alsa-devel] " Takashi Iwai
2005-08-22 20:38 ` James Courtier-Dutton
2005-08-22 21:54 ` Lee Revell
2005-08-23 20:41 ` Peter Zubaj
2005-08-23 18:48 ` Lennart Sorensen
2005-08-23 22:12 ` Lee Revell
2005-08-23 21:39 ` Lee Revell [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=1124833199.30517.23.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=pzubaj@gaya.sk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox