Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@ivitera.com>
To: alsa-devel@alsa-project.org
Subject: Re: Creative Sound Blaster X-Fi and X-Fi Titanium	Series Linux 32bit/64bit Driver Source released
Date: Wed, 12 Nov 2008 11:05:49 +0100	[thread overview]
Message-ID: <491AAA7D.3030604@ivitera.com> (raw)
In-Reply-To: <fd3eb9bf0811111347n55540926y54fcd871306491f2@mail.gmail.com>

Vedran Miletić wrote:
> 2008/11/11 Bjoern Olausson <lkmlist@gmail.com>:
>> On Tue, Nov 11, 2008 at 19:33, James Courtier-Dutton
>> <James@superbug.co.uk> wrote:
>>> All the good contacts I had at Creative have left the company.
>>> From what I understand of how the company works internally, is that the
>>> only reason they have this open source driver is because some large
>>> customer of theirs required it. They have no interest in what happens to
>>> the driver over and above supporting the one customer that requested it.
>>> I therefore doubt that they will make any contact with us regarding
>>> getting the driver into the kernel. If that was the case, they would
>>> have approached us earlier.
>>>
>>> Kind Regards
>>>
>>> James
>>>
>> If you are right, that would be a straight hit in the face of every
>> Linux X-Fi user and the OpenSource community.
>> So sad... but thanks for the info.
>>
>> Lets hope the best.
>>
>> Bjoern
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>
> 
> Then show your appreciation to Creative by never ever buying any of
> their products again. That's what I'm going to do.
> 

Honestly, at least they did something. There are sound card 
manufacturers that never released a single line of code, nor did they 
offer NDAs to ALSA developers.

If it is for a large customer, I cannot imagine he would be satisfied 
with the current state of the released driver. But I may be wrong, as 
often :)


Pavel.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2008-11-12 10:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 15:46 Creative Sound Blaster X-Fi and X-Fi Titanium Series Linux 32bit/64bit Driver Source released Bjoern Olausson
2008-11-06 17:20 ` The Source
2008-11-06 17:26   ` Takashi Iwai
2008-11-06 17:56     ` Brendan Pike
2008-11-06 19:34     ` Bjoern Olausson
2008-11-10  7:45     ` Takashi Iwai
2008-11-10  7:47       ` The Source
2008-11-11  5:14       ` Bjoern Olausson
2008-11-11  7:55         ` Bjoern Olausson
2008-11-11  8:10           ` Takashi Iwai
2008-11-11 18:33             ` James Courtier-Dutton
2008-11-11 19:36               ` Bjoern Olausson
2008-11-11 21:47                 ` Vedran Miletić
2008-11-12 10:05                   ` Pavel Hofman [this message]
2008-11-12 17:46                   ` Bjoern Olausson
2008-11-06 17:42   ` Brendan Pike
2008-11-06 23:36 ` Toby
2008-11-07  4:42   ` The Source
2008-11-07  5:02     ` The Source
2008-11-07 19:08     ` Bjoern Olausson
2008-11-07 23:28       ` Sebastian Schneider
2008-11-08  5:32       ` The Source
2008-11-09 23:32         ` Bjoern Olausson
2008-11-13 20:09           ` Sebastian Schneider

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=491AAA7D.3030604@ivitera.com \
    --to=pavel.hofman@ivitera.com \
    --cc=alsa-devel@alsa-project.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