From: Ctirad Fertr <c.fertr@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: Will there ever be emu20k1/x-fi support in Alsa?
Date: Mon, 6 Oct 2008 08:39:39 +0200 [thread overview]
Message-ID: <200810060839.39256.c.fertr@gmail.com> (raw)
In-Reply-To: <20081005215927.3a907b59@darius>
Dne Monday 06 of October 2008 03:59:27 Brendan Pike napsal(a):
> Yes, just pay James Courtier-Dutton a lot of money to write a driver. If
> you're in the EMU or X-Fi camp, you should of moved on by now. Creative
> are providing NDA'd specs to the wrong person at ALSA. (See EMU
> 0202/0404, and now X-Fi support)
>
> Don't bother contacting him either, it goes straight to /dev/null.
That was quite rough, but kind of true :(
That was exactly the reason, that I gived up any efforts to improve E-MU PCI
driver.
> Bottom line, if one can't write a driver or don't have time, don't
> bother to NDA specifications okay? It just slows things down.
Definitely.
---
Ctirad
next prev parent reply other threads:[~2008-10-06 6:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 23:14 Will there ever be emu20k1/x-fi support in Alsa? Ted T. Logian
2008-10-06 1:59 ` Brendan Pike
2008-10-06 6:39 ` Ctirad Fertr [this message]
2008-10-06 19:01 ` Ted T. Logian
2008-10-06 8:35 ` Vedran Miletić
2008-10-06 18:56 ` Ted T. Logian
2008-10-07 14:50 ` Vedran Miletić
2008-10-06 21:25 ` Sebastian Schneider
2008-10-07 6:32 ` Ted T. Logian
2008-10-07 6:41 ` The Source
2008-10-08 0:46 ` Ted T. Logian
2008-10-08 4:22 ` Brendan Pike
2008-10-08 4:54 ` The Source
2008-10-09 10:00 ` Takashi Iwai
2008-10-09 10:06 ` The Source
2008-10-09 11:54 ` Takashi Iwai
2008-10-09 17:27 ` Ted T. Logian
-- strict thread matches above, loose matches on Subject: below --
2008-10-08 1:39 Sebastian Schneider
2008-10-09 6:23 The Source
2008-10-09 17:37 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=200810060839.39256.c.fertr@gmail.com \
--to=c.fertr@gmail.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 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.