From: Sven Luther <sven.luther@wanadoo.fr>
To: Ken Moffat <ken@kenmoffat.uklinux.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Is emu10k1 broken in ppc ?
Date: Fri, 4 Mar 2005 18:00:26 +0100 [thread overview]
Message-ID: <20050304170026.GA4688@pegasos> (raw)
In-Reply-To: <Pine.LNX.4.58.0503040042380.20574@ppg_penguin.kenmoffat.uklinux.net>
On Fri, Mar 04, 2005 at 01:01:40AM +0000, Ken Moffat wrote:
> First noticed this earlier this week, trying to upgrade my iBook from
> 2.6.8 to 2.6.11-rc5, using a debian config. At that point, it didn't
> seem important to me. Bit me again tonight when I tried to get my
> AmigaOne up to 2.6.10 from 2.6.9 using my existing config. The case
> labels are SNDRV_EMU10K1_CODE_POKE and SNDRV_EMU10K1_CODE_PEEK, neither
> the header nor the code changed between 2.6.9 and 2.6.10.
This was fixed in the debian kernel. Try ou debian's kernel-source-2.6.10, or
get the patch from debian's svn.debian.org kernel repo archive.
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-03-04 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 1:01 Is emu10k1 broken in ppc ? Ken Moffat
2005-03-04 17:00 ` Sven Luther [this message]
2005-03-04 17:37 ` Ken Moffat
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=20050304170026.GA4688@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=ken@kenmoffat.uklinux.net \
--cc=linuxppc-dev@ozlabs.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).