From: James Courtier-Dutton <James@superbug.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Bjoern Olausson <lkmlist@gmail.com>
Subject: Re: Creative Sound Blaster X-Fi and X-Fi Titanium Series Linux 32bit/64bit Driver Source released
Date: Tue, 11 Nov 2008 18:33:18 +0000 [thread overview]
Message-ID: <4919CFEE.4060604@superbug.co.uk> (raw)
In-Reply-To: <s5hfxlyzns4.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Tue, 11 Nov 2008 08:55:04 +0100,
> Bjoern Olausson wrote:
>> On Tue, Nov 11, 2008 at 06:14, Bjoern Olausson <lkmlist@gmail.com> wrote:
>>>> Did take a quick glance through their code now.
>>>> A good news is that it's much better than I was concerned.
>>>> There are a few things to be fixed / discussed, but basically it
>>>> shouldn't be that difficult.
>>>>
>>>> Can anyone have a contact with them? If they are interested in the
>>>> upstream merging, please give my name and address as the contact
>>>> person.
>>>>
>>> I posted in the driver feedback forum and asked them to get in contact
>>> with you or me, so lets see what happens.
>>>
>>> http://forums.creative.com/creativelabs/board/message?board.id=soundblaster&view=by_date_ascending&message.id=132606#M132606
>>>
>> Seems there is no way to get in contact with the Devs directly, no
>> bugtracker, nothing... just that forum... (but I guess no dev is
>> ?allowed/willing? to write in this forum) I don't really understand
>> the way creative communicates with it's customers... so lets see if
>> someone will contact you... my guess is no...
>
> Well, let's hope it.
>
>
> thanks,
>
> Takashi
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
next prev parent reply other threads:[~2008-11-11 18:33 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 [this message]
2008-11-11 19:36 ` Bjoern Olausson
2008-11-11 21:47 ` Vedran Miletić
2008-11-12 10:05 ` Pavel Hofman
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=4919CFEE.4060604@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=lkmlist@gmail.com \
--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.