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: Thu, 06 Nov 2008 20:20:09 +0300 [thread overview]
Message-ID: <49132749.4040908@gmail.com> (raw)
In-Reply-To: <5501535d0811060746y60d18e6boc8c5ad34a63fb92b@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
Bjoern Olausson пишет:
> 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)
>
> http://forums.creative.com/creativelabs/board/message?board.id=soundblaster&thread.id=132288
>
> http://support.creative.com/downloads/download.aspx?nDownloadId=10792
>
> Kind regards
> Bjoern
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
>
Tried that driver. It oopses for my system (2.6.26.6-79.fc9.x86_64). I
attached dmesg output with oops trace log. Since that driver is open
source, this log might be interesting for you. Pergaps you can get the
driver to working state?
[-- Attachment #2: dmesg.out.bz2 --]
[-- Type: application/x-bzip, Size: 11117 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2008-11-06 17:20 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 [this message]
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
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=49132749.4040908@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