From: Brendan Pike <spike@spykes.net>
To: "Ted T. Logian" <tedtheologian@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Will there ever be emu20k1/x-fi support in Alsa?
Date: Wed, 8 Oct 2008 00:22:08 -0400 [thread overview]
Message-ID: <20081008002208.464cb3aa@darius> (raw)
In-Reply-To: <1223426782.11647.5.camel@home>
On Tue, 07 Oct 2008 19:46:22 -0500
"Ted T. Logian" <tedtheologian@gmail.com> wrote:
> Yes, but it is better than nothing, and perhaps some of that is a
> limitation of oss4:).
>
> On Tue, 2008-10-07 at 10:41 +0400, The Source wrote:
>
> > That driver isn't too good unfortunately. No surround support, sample
> > rate stuck at 96000Hz and is read-only (this makes apps that require
> > explicit sample rate to fail to use sound), no pulse-audio compatibility
> > (pulse-audio fails to load oss modules).
> >
> > Ted T. Logian ?????:
> > > >From what I understand, they did not use creative code/license for the
> > > oss4 support, so I wouldn't see why not.
> > >
> > > On Mon, 2008-10-06 at 23:25 +0200, Sebastian Schneider wrote:
> > >
> > >
> > >> Isn't it a question of the license? I mean is it allowed just to port the OSS Code with the Creative Part to Alsa?
> > >>
> > >>
> > >>> I had to ask because oss4 has had emu20k1/x-fi support for a long time
> > >>> now. However, it has the obvious limitations of oss4 and also you
> > >>> cannot use usb microphones, so I can't use skype which I'd really like
> > >>> to do.
> > >>>
> > >>>
Porting the oss4 driver over to ALSA would be a start until someone
can get hold of the datasheets to make it a proper driver with
hardware mixing and all. Anyone up to the task that we can donate
money to buy hardware or actual hardware to?
The newer PCIe EMU20K2 X-Fi Titaniums are the ones that are supposed to
have the intel-hda-audio backwards compatibility, but the older X-Fi's
based on the EMU20K1 do not. I guess this compatibility is a Vista
requirement so it appears on the new metal cladded X-Fi models.
Then there's the "fake" X-Fi's based on the CA0106 that
are supported by ALSA already. Lets not confuse those.
next prev parent reply other threads:[~2008-10-08 4:22 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
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 [this message]
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=20081008002208.464cb3aa@darius \
--to=spike@spykes.net \
--cc=alsa-devel@alsa-project.org \
--cc=tedtheologian@gmail.com \
/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.