From: Spike <spike@spykes.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, daedra <daedra@charter.net>
Subject: Re: emu20k1 in 1.0.17?
Date: Fri, 27 Jun 2008 20:49:37 -0400 [thread overview]
Message-ID: <20080627204937.0d5b0e60@darius> (raw)
In-Reply-To: <s5h1w2l8qjr.wl%tiwai@suse.de>
On Wed, 25 Jun 2008 17:47:36 +0200
Takashi Iwai <tiwai@suse.de> wrote:
> At Sat, 21 Jun 2008 01:35:38 -0700,
> daedra wrote:
> >
> > I was just wondering if there is a chance of the emu20k1 driver making
> > it's way into 1.0.17?
>
> Very unlikely...
>
> CA0110 (HD-audio port) would be easy to support. I already have a
> test patch on my unstable git tree. But the real DSP seems hard, and
> I have no spec, too. James could comment on this more.
>
So James had the specs for the 20K1 for over a month now,
and there hasn't been any news for equally as long. I assume this
datasheet has an NDA attached, but James hasn't made any mention of
that.
So which is it? You have the specs, Creative themselves state this, so
is the writing of this driver going to be a 1 man job? It would explain
the delay.
If the specs were public, we'd probably have a driver by now, but
nobody has a clue if they're in NDA or not, as James wont talk about it.
Creative also states that their own driver will be all source by the
end of this year, so maybe James has no intention on reinventing the
wheel. Maybe he is behind rewriting this driver to open source, who
knows. Nobody knows a darn thing.
Bren
next prev parent reply other threads:[~2008-06-28 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 8:35 emu20k1 in 1.0.17? daedra
2008-06-25 15:47 ` Takashi Iwai
2008-06-28 0:49 ` Spike [this message]
2008-06-28 8:39 ` Takashi Iwai
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=20080627204937.0d5b0e60@darius \
--to=spike@spykes.net \
--cc=alsa-devel@alsa-project.org \
--cc=daedra@charter.net \
--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.