From: Lee Revell <rlrevell@joe-job.com>
To: sclark46@earthlink.net
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.12 sound problem
Date: Wed, 27 Jul 2005 00:23:58 -0400 [thread overview]
Message-ID: <1122438238.13598.19.camel@mindpipe> (raw)
In-Reply-To: <42E6C8DB.4090608@earthlink.net>
On Tue, 2005-07-26 at 19:35 -0400, Stephen Clark wrote:
> Additional info I don't see any interrupts in /proc/interrupts for the
> Allegro which is on int 5.
> I just tried the same laptop with knoppix and a 2.4.27 kernel and sound
> works great and I do
> see interrupts for Allegro on int 5.
So the same ALSA driver works on 2.6 but fails on 2.4? Or are you
really saying 2.4 + the OSS driver works and 2.6 + ALSA does not?
Lee
next prev parent reply other threads:[~2005-07-27 4:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 23:35 2.6.12 sound problem Stephen Clark
2005-07-27 4:23 ` Lee Revell [this message]
2005-07-27 15:31 ` Stephen Clark
2005-07-27 8:26 ` Takashi Iwai
2005-07-27 15:31 ` Stephen Clark
2005-07-29 8:41 ` Andrew Morton
2005-07-29 9:05 ` [PATCH] mm/slab.c : prefetchw the start of new allocated objects Eric Dumazet
2005-07-29 9:17 ` Andrew Morton
2005-07-29 10:08 ` Ingo Molnar
2005-07-30 19:31 ` David S. Miller
2005-07-30 3:13 ` 2.6.12 sound problem Stephen Clark
2005-07-30 15:56 ` Stephen Clark
2005-07-31 19:25 ` 2.6.13rc4 hang Stephen Clark
2005-08-01 13:11 ` Stephen Clark
-- strict thread matches above, loose matches on Subject: below --
2005-08-01 3:06 2.6.12 sound problem Yuan, Hang
2005-07-29 10:21 Yuan, Hang
2005-07-29 12:41 ` Stephen Clark
2005-07-30 3:05 ` Stephen Clark
2005-07-26 23:34 Stephen Clark
2005-07-27 7:14 ` Jaroslav Kysela
2005-07-28 14:05 ` Stephen Clark
2005-07-28 14:11 ` Stephen Clark
2005-07-26 17:08 Stephen Clark
2005-07-25 19:16 Stephen Clark
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=1122438238.13598.19.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sclark46@earthlink.net \
/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.