Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: The Source <thesourcehim@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Creative Sound Blaster X-Fi and X-Fi Titanium	Series Linux 32bit/64bit Driver Source released
Date: Fri, 07 Nov 2008 07:42:42 +0300	[thread overview]
Message-ID: <4913C742.9040107@gmail.com> (raw)
In-Reply-To: <8fe68c970811061536n52c6c819v58145401002555be@mail.gmail.com>

Toby пишет:
> 2008/11/7 Bjoern Olausson <lkmlist@gmail.com>:
>   
>> Creative released a driver today....
>> I am hasitating to install it.. the last one was so crappy and I just
>> installed my gentoo new ;-)
>>
>> But it looks really like the SOURCE, so maybe it will help to pimp the
>> ALSA driver (would rather see an implementation in alsa then an driver
>> from Creative)
>>     
>
> Is the new driver providing an ALSA device, or an OSS-style /dev/dsp one?
>
> Personally I'd rather see an open-source driver make it into ALSA to
> support the X-Fi, rather than relying upon Creative's terrible quality
> and dreadful timeliness.
>
> I'll try out the Creative driver on the weekend, and see if it works
> where the ALSA one doesn't. (I just get loops of static from the
> experimental ALSA driver.. it's like a memory ring buffer somewhere is
> *meant* to be getting filled with an audio stream, but isn't - but the
> card is still playing from it.)
>
> Cheers.
> Toby
>
>   
It was incompatibility with older kernels. Updated to 2.6.27 and driver 
works now. But no 5.1 support again :(
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2008-11-07  4:42 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
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 [this message]
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=4913C742.9040107@gmail.com \
    --to=thesourcehim@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox