From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Timur Tabi <timur@freescale.com>, alsa-devel@alsa-project.org
Subject: Re: Any OSS changes from kernel 2.6.21 to 2.6.23? Something broke.
Date: Fri, 02 Nov 2007 18:11:05 +0100 [thread overview]
Message-ID: <1194023465.19772.1219244387@webmail.messagingengine.com> (raw)
In-Reply-To: <472B4416.8060009@freescale.com>
Timur Tabi wrote:
> I have a customer who says that mplayer (using OSS) does not work when he tries
> a kernel based on 2.6.23-rc4, but it works when he uses a kernel based on
> 2.6.21. Everything else is the same (including the version of alsa-lib), so I
> presume something broke in the OSS emulation in the kernel.
It could also be a change in the driver.
And it would be nice to know what "does not work" actually means.
> Is it possible to back-level the ALSA support in the kernel itself?
The alsa-kernel tree is only compatible with the current development
kernel.
The alsa-driver package works with older kernels, but must be compiled
seperately.
> Can I just download ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.XX.tar.bz2
> and follow the instructions in the INSTALL file?
Yes.
> If you update the kernel, are you supposed to use the latest alsa-lib as well?
No; the kernel and lib versions are more or less independent.
HTH
Clemens
next prev parent reply other threads:[~2007-11-02 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 15:36 Any OSS changes from kernel 2.6.21 to 2.6.23? Something broke Timur Tabi
2007-11-02 17:11 ` Clemens Ladisch [this message]
2007-11-02 18:22 ` Timur Tabi
2007-11-03 16:51 ` James Courtier-Dutton
2007-11-04 15:15 ` Timur Tabi
2007-11-05 14:27 ` Takashi Iwai
2007-11-08 0:15 ` Timur Tabi
2007-11-08 7:34 ` Clemens Ladisch
2007-11-08 17:35 ` Timur Tabi
2007-11-08 19:33 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2011-01-31 3:09 Raymond Yau
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=1194023465.19772.1219244387@webmail.messagingengine.com \
--to=cladisch@fastmail.net \
--cc=alsa-devel@alsa-project.org \
--cc=timur@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).