From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andreas Schwab <schwab@suse.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: tas: I2C byte write failed
Date: 09 Aug 2003 10:54:38 +0200 [thread overview]
Message-ID: <1060419278.653.13.camel@gaston> (raw)
In-Reply-To: <m3he4r8cfs.fsf@whitebox.as.local>
On Sat, 2003-08-09 at 10:25, Andreas Schwab wrote:
> Whenever my iBook wakes up I get the message "tas: I2C byte write
> failed" and sound remains silent. This is with 2.4.21-ben2 (TAS3004
> driver V 0.3), but happens with previous versions as well. Could this
> be a problem of wrong reinitialisation order during wakeup (both
> dmasound and i2c are compiled as module)? Resetting the volume makes
> sound work again.
Might be, I'll investigate. Thanks.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-08-09 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-09 8:25 tas: I2C byte write failed Andreas Schwab
2003-08-09 8:54 ` Benjamin Herrenschmidt [this message]
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=1060419278.653.13.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schwab@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 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).