From: Grzesiek Sedek <grzesiek@mi2.hr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA ../alsa-kernel/ppc/keywest.c:84: tumbler: cannot initialize the MCS
Date: 30 Jun 2003 14:17:00 +0100 [thread overview]
Message-ID: <1056979019.3742.8.camel@localhost> (raw)
In-Reply-To: <s5hsmprlns0.wl@alsa2.suse.de>
Yes both i2c-keywest and i2c-core are build and loaded.
I'm really puzzled-I never had any problems like that. I've build few
kernels since alsa stopped using old working .config's and still no
luck.
Thanks
On Mon, 2003-06-30 at 14:04, Takashi Iwai wrote:
> At 28 Jun 2003 16:50:55 +0100,
> Grzesiek Sedek wrote:
> >
> > I had my alsa running fine for a while at some point audio stop working
> > (must been afer one of upgrades to 9.4 on debian ppc sid)
> > this is dmesg error I'm getting:
> >
> > ALSA ../alsa-kernel/ppc/keywest.c:84: tumbler: cannot initialize the MCS
> >
> > modules are loading ok but no sound.
> > Thanks for any help.
>
> did you load/build the i2c-keywest driver, too?
> the pmac tumbler/snapper requires this for controlling the chip over
> i2c.
>
>
> Takashi
--
Grzesiek Sedek <grzesiek@mi2.hr>
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
next prev parent reply other threads:[~2003-06-30 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-28 15:50 ALSA ../alsa-kernel/ppc/keywest.c:84: tumbler: cannot initialize the MCS Grzesiek Sedek
2003-06-30 13:04 ` Takashi Iwai
2003-06-30 13:17 ` Grzesiek Sedek [this message]
2003-07-02 11:16 ` Takashi Iwai
2003-07-02 13:35 ` Grzesiek Sedek
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=1056979019.3742.8.camel@localhost \
--to=grzesiek@mi2.hr \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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.