All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: alsa-devel@alsa-project.org
Subject: Any OSS changes from kernel 2.6.21 to 2.6.23? Something broke.
Date: Fri, 02 Nov 2007 10:36:54 -0500	[thread overview]
Message-ID: <472B4416.8060009@freescale.com> (raw)

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.  Unfortunately, our 
git repositories for these trees are not compatible, so I can't use git-bisect 
to narrow the problem down.

Is it possible to back-level the ALSA support in the kernel itself?  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?

If you update the kernel, are you supposed to use the latest alsa-lib as well? 
For a given kernel, how do I know what the right version of alsa-lib is?

-- 
Timur Tabi
Linux kernel developer at Freescale

             reply	other threads:[~2007-11-02 15:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 15:36 Timur Tabi [this message]
2007-11-02 17:11 ` Any OSS changes from kernel 2.6.21 to 2.6.23? Something broke Clemens Ladisch
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=472B4416.8060009@freescale.com \
    --to=timur@freescale.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 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.