From: Lee Revell <rlrevell@joe-job.com>
To: reetesh chandran <reeteshchandran@yahoo.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Alsa driver compatible with 2.6.18 kernel
Date: Fri, 10 Apr 2009 20:45:55 -0400 [thread overview]
Message-ID: <75b66ecd0904101745x43b5b6f2m34fb1ccbb0963bc0@mail.gmail.com> (raw)
In-Reply-To: <506017.79962.qm@web30005.mail.mud.yahoo.com>
On Fri, Apr 10, 2009 at 12:54 PM, reetesh chandran
<reeteshchandran@yahoo.com> wrote:
> Hello all,
>
> I have a 2.6.18 kernel and I am using 1.0.12rc1 alsa driver. I am facing some issues and would like to get a newer alsa driver. I cant change the linux kernel version. Do you know which is the latest alsa driver which is supported on linux 2.6.18 ? How do I find that out ?
The latest should work. New ALSA releases are backwards compatible
with old kernels.
Lee
next prev parent reply other threads:[~2009-04-11 0:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 16:54 Alsa driver compatible with 2.6.18 kernel reetesh chandran
2009-04-11 0:45 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-11 14:07 reetesh chandran
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=75b66ecd0904101745x43b5b6f2m34fb1ccbb0963bc0@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@alsa-project.org \
--cc=reeteshchandran@yahoo.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