From: Uli <psycho@foex-gaming.com>
To: alsa-devel@alsa-project.org
Subject: ALSA works, OSS doesnt
Date: Sat, 05 Aug 2006 21:49:07 +0200 [thread overview]
Message-ID: <44D4F633.3060302@foex-gaming.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
since i updated my gentoo box from kernel 2.6.16 to 2.6.17 all apps
using OSS for sound didnt work. Skype pitched the sound, Firefox had
gaps and so on.
I did some git-bisect to find out what broke my sound and got compile
errors...
Here is what i got to:
- ------------------------------------------------------
21a3479a0b606d36fe24093f70a1c27328cec286 is first bad commit
diff-tree 21a3479a0b606d36fe24093f70a1c27328cec286 (from
153abaa4ff0500070a282dd0868367d69388d527)
Author: Jaroslav Kysela <perex@suse.cz>
Date: Fri Jan 13 09:12:11 2006 +0100
[ALSA] PCM midlevel & PCM OSS - make procfs & OSS plugin code optional
Modules: ALSA Core,PCM Midlevel,ALSA<-OSS emulation,USB generic driver
1) The verbose procfs code for the PCM midlevel and usb audio
can be removed now (more patches will follow).
CONFIG_SND_VERBOSE_PROCFS
2) The PCM OSS plugin system can be also compiled optionaly.
CONFIG_SND_PCM_OSS_PLUGINS
Signed-off-by: Jaroslav Kysela <perex@suse.cz>
:040000 040000 de2951ee7fcc2dd79e4b05f9929689e4c236eb66
6b0d7ac583b44b7a86dbd223b4e5b797333ea2eb M include
:040000 040000 e8a248df599daeb773720babe3b9bd0740e3a813
7c182a880af29f6b19a3ae7479ff1d9ec35f5aa4 M sound
- ---------------------------------------------
0534ab4279bd25e2d0a888af07466446dac05d74 is first bad commit
diff-tree 0534ab4279bd25e2d0a888af07466446dac05d74 (from
9d83911ac082c6d63c1c08f235349113d8c1d0a3)
Author: Takashi Iwai <tiwai@suse.de>
Date: Fri Jan 13 12:09:12 2006 +0100
[ALSA] Clean up pcm-oss plugins
Modules: ALSA<-OSS emulation
Clean up pcm-oss plugin codes.
Removed dead codes, and simplified route/rate plugins.
Signed-off-by: Takashi Iwai <tiwai@suse.de>
:040000 040000 a7cf54730a307149c77418ca229bb5604e69ec5e
8f891f51f762d0468b6c59e839b11358be3b0d3a M sound
- -----------------------------------------------
I'm totaly sure one of this comitts broke the sound because i had some
compile error and copying the whole directory and continued in one with
git bisect bad and in the other with good. So i got two 'solutions' but
i hope at least this can help fix the bug.
If i can do any more for fixing this, just ask.
If this bug is already fixed: I'm sorry, just ignore this mail.
Uli Schlachter
- --
Who is this LAN and why makes he so many partys?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE1PYJABixOSrV998RAj9LAJ9PrpC6OLfW8SoGj7+rl0LF9qLFLwCfSokN
SvDX3vPKYejAak5igLkamTQ=
=pIvA
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2006-08-05 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 19:49 Uli [this message]
2006-08-07 12:36 ` ALSA works, OSS doesnt Takashi Iwai
2006-08-07 12:38 ` 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=44D4F633.3060302@foex-gaming.com \
--to=psycho@foex-gaming.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox