From: David van Hoose <davidvh@cox.net>
To: andersen@codepoet.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ALSA and 2.4.x
Date: Thu, 24 Apr 2003 22:40:57 -0500 [thread overview]
Message-ID: <3EA8AE49.7020705@cox.net> (raw)
In-Reply-To: <20030424212508.GI14661@codepoet.org>
Erik Andersen wrote:
> On Thu Apr 24 2003 - 08:35:48 EST, David van Hoose wrote:
>
>>Is there a ALSA backport to 2.4.x anywhere?
>
> I was crazy enough to take ALSA 0.9.2 and made it into a patch vs
> 2.4.x a week or two ago. I just prefer to have ALSA be part of
> the kernel rather than needing to compile it seperately all the
> time. The patch, along with various other things, is included as
> part of my 2.4.21-rc1-erik kernel:
>
> http://codepoet.org/kernel/
>
> This is what I am running locally, and it works for me,
Works *very* well. I now have sound. I'd recommend adding the ALSA
documentation from 2.5.x to the patch. It is easier than trying to
navigate through alsa-project.org for setup information. It would be
nice if ALSA was placed into 2.4.x as soon as possible. Doesn't require
any extra patches beyond the ones for the kernel.
Thanks for the help!
David
next prev parent reply other threads:[~2003-04-25 3:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 21:25 ALSA and 2.4.x Erik Andersen
2003-04-25 3:40 ` David van Hoose [this message]
2003-04-25 12:01 ` Marc-Christian Petersen
2003-04-25 12:10 ` Marc-Christian Petersen
2003-04-30 9:02 ` Erik Andersen
2003-04-30 20:07 ` David van Hoose
2003-04-30 20:22 ` Erik Andersen
2003-04-30 20:36 ` Willy Tarreau
2003-04-30 20:50 ` Erik Andersen
2003-05-01 0:09 ` David van Hoose
2003-04-25 12:24 ` Erik Andersen
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 13:35 David van Hoose
2003-04-24 13:43 ` Marc-Christian Petersen
2003-04-24 13:56 ` Maciej Soltysiak
2003-04-24 13:49 ` Con Kolivas
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=3EA8AE49.7020705@cox.net \
--to=davidvh@cox.net \
--cc=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).