From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: Michael Buesch <mb@bu3sch.de>,
Roger Leigh <rleigh@whinlatter.ukfsn.org>,
linux-kernel@vger.kernel.org,
Dennis Munsie <dmunsie@cecropia.com>
Subject: Re: radeonfb i2c regression post-2.6.18.
Date: Sun, 25 Nov 2007 09:25:35 +1100 [thread overview]
Message-ID: <1195943135.7195.61.camel@pasglop> (raw)
In-Reply-To: <20071124232035.0f46d530@hyperion.delvare>
> Very strange indeed. Another possibility is that there is a hardware
> monitoring chip connected to one of the Radeon adapter's I2C buses, and
> that holding the I2C lines prevents reading from it, so whatever is
> responsible for controlling the temperature prefers to play it safe and
> shuts everything down. Somehow it seems more realistic than an actual
> overheating (3 seconds is a very short period of time for that), but
> we'd need the exact schematics of the hardware, and the details of the
> thermal control system, to validate this theory.
>
> Anyway, no need to worry anymore now that the bug is fixed :)
Actually, that's a possibility yes, though generally Apple put all temp.
monitoring chips elsewhere, it could well be the case.
Ben.
next prev parent reply other threads:[~2007-11-24 22:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 23:16 radeonfb i2c regression post-2.6.18 Benjamin Herrenschmidt
2007-11-21 9:42 ` Roger Leigh
2007-11-21 19:58 ` Benjamin Herrenschmidt
2007-11-21 20:13 ` Michael Buesch
2007-11-21 20:17 ` Benjamin Herrenschmidt
2007-11-21 23:56 ` Roger Leigh
2007-11-22 0:00 ` Benjamin Herrenschmidt
2007-11-23 16:00 ` Michael Buesch
2007-11-23 22:29 ` Jean Delvare
2007-11-24 1:11 ` Benjamin Herrenschmidt
2007-11-24 9:29 ` Jean Delvare
2007-11-24 14:18 ` Michael Buesch
2007-11-24 22:20 ` Jean Delvare
2007-11-24 22:25 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-18 21:58 Roger Leigh
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=1195943135.7195.61.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=dmunsie@cecropia.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=rleigh@whinlatter.ukfsn.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