All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Question on ALSA versions
Date: Thu, 04 Nov 2004 14:32:09 -0500	[thread overview]
Message-ID: <1099596730.1617.61.camel@krustophenia.net> (raw)
In-Reply-To: <cmciu9$hsn$1@sea.gmane.org>

On Thu, 2004-11-04 at 11:42 +0500, Alexander E. Patrakov wrote:
> Hello,
> 
> I have the following question. Is it OK to have mismatched versions of ALSA
> drivers (e.g. 1.0.4, from linux-2.6.8.1) and libs (1.0.6)? This _seems_ to
> work, and I see the code to support various versions of the kernel PCM
> protocol in the library, but I want to see official words from developers.

This is not guaranteed to work, and could lead to all kinds of weird
problems.  Alsa-lib is the mechanism by which changes in the kernel side
ALSA are hidden from userspace.  They expect to be the same version.

In practice it usually works but there have been some specific incidents
where this caused problems.  For example when a major change is made to
a driver the hardware specific parts of alsa-lib will be updated to
reflect the change.

Lee



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

  reply	other threads:[~2004-11-04 19:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04  6:42 Question on ALSA versions Alexander E. Patrakov
2004-11-04 19:32 ` Lee Revell [this message]
2004-11-05  4:53   ` Alexander E. Patrakov
2004-11-05  6:03     ` Jaroslav Kysela
2004-11-05  9:33       ` Alexander E. Patrakov

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=1099596730.1617.61.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=patrakov@ums.usu.ru \
    /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.