From: Martin Habets <errandir_news@mph.eclipse.co.uk>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.6.5/iBook G3: Oops on resume from sleep
Date: Tue, 6 Apr 2004 13:01:58 +0100 [thread overview]
Message-ID: <20040406120158.GA7444@palantir8> (raw)
In-Reply-To: <20040406073741.GA4008@fpirisp.portsdebalears.com>
On Tue, Apr 06, 2004 at 09:37:41AM +0200, Kiko Piris wrote:
> It seems I do:
>
> ---8<---
> 0 [Snapper ]: PMac Snapper - PowerMac Snapper
> PowerMac Snapper (Dev 24) Sub-frame 0
> --->8---
Good, same chip I have.
> > This capture_source thing was added pretty recently.
>
> I don't quite understand you, sorry.
Well, the code is so new that the bug fixes have not made it into the
kernel yet. But they are in the alsa cvs node.
What I did is pick up revision 1.29 (the latest) from
http://cvs.sourceforge.net/viewcvs.py/alsa/alsa-kernel/ppc/tumbler.c
Make a backup of your existing tumbler.c file, just in case... Put the
new one in an recompile.
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-06 12:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 21:53 2.6.5/iBook G3: Oops on resume from sleep Kiko Piris
2004-04-05 23:13 ` Martin Habets
2004-04-06 7:37 ` Kiko Piris
2004-04-06 12:01 ` Martin Habets [this message]
2004-04-06 12:43 ` Kiko Piris
2004-04-06 22:18 ` Martin Habets
2004-04-07 15:18 ` Kiko Piris
2004-04-06 0:52 ` Benjamin Herrenschmidt
2004-04-07 19:17 ` Aaron Lunansky
2004-04-07 22:49 ` Benjamin Herrenschmidt
2004-04-08 13:14 ` Aaron Lunansky
2004-04-09 6:03 ` Benjamin Herrenschmidt
2004-04-09 13:47 ` Aaron Lunansky
2004-04-09 23:52 ` Benjamin Herrenschmidt
2004-04-10 1:20 ` [resolved] " Aaron Lunansky
2004-04-10 1:47 ` Benjamin Herrenschmidt
2004-04-13 10:36 ` Michael Schmitz
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=20040406120158.GA7444@palantir8 \
--to=errandir_news@mph.eclipse.co.uk \
--cc=linuxppc-dev@lists.linuxppc.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).