From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: radeonfb monid i2c bus
Date: Fri, 06 Jun 2008 23:50:18 +1000 [thread overview]
Message-ID: <1212760218.12464.33.camel@pasglop> (raw)
In-Reply-To: <20080606120151.7976df45@hyperion.delvare>
On Fri, 2008-06-06 at 12:01 +0200, Jean Delvare wrote:
> Hi Ben,
>
> Can you explain what is the "monid" i2c bus on Radeon adapters? I have
> two Radeon chips here, an M6 in my old laptop and a 9200 in my desktop
> system. On the M6 there is nothing on the monid bus. On the 9200, the
> monid bus doesn't even work, every access results in timeout. The
> radeonfb driver doesn't even look for EDID EEPROMs on that bus (except
> in debug code.)
>
> So I'm curious why you create this i2c bus if you don't need it.
> Have you ever seen a Radeon adapter where there is something on that
> bus?
The BIOS connector tables might make us use it. Otherwise, it tends to
have the external TMDS transmitter on it for which we'll one day get
proper support for re-initializing on wakeup from sleep...
Ben.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
next prev parent reply other threads:[~2008-06-06 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 10:01 radeonfb monid i2c bus Jean Delvare
2008-06-06 13:46 ` Alex Deucher
2008-06-06 13:50 ` Benjamin Herrenschmidt [this message]
2008-06-08 14:20 ` Jean Delvare
2008-06-08 22:48 ` Jimmy.Jazz
2008-06-09 5:15 ` Alex Deucher
2008-06-09 7:14 ` Jean Delvare
2008-06-09 13:02 ` Alex Deucher
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=1212760218.12464.33.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=khali@linux-fr.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).