linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] radeonfb: Let hwmon driver probe the "monid" I2C bus
Date: Thu, 13 Jan 2011 08:56:57 +0000	[thread overview]
Message-ID: <20110113095657.20b3f181@endymion.delvare> (raw)
In-Reply-To: <20110111162352.5a634e9e@endymion.delvare>

Hi Ben,

On Thu, 13 Jan 2011 15:50:10 +1100, Benjamin Herrenschmidt wrote:
> On Thu, 2011-01-13 at 14:44 +1000, Dave Airlie wrote:
> > The radeon BIOS actually contains a table to tell us what chip is on
> > the bus,
> > in the KMS driver we read this table and load the appropriate hwmon
> > device,
> > 
> > There could possibly be other things on this bus than hw monitor
> > devices.
> > 
> > Though radeonfb should be considered mostly dead. 
> 
> I want to test that on a few powermacs first. "probing" i2c can be
> destructive and f* knows what Apple put on those busses on some
> machines.

If this is a concern to you, I'd be fine excluding CONFIG_PPC from the
change. Or are you worried about Intel Mac machines too? If there's an
easy way to spot all powermac machines, we can use that too, just let
me know how.

> Haven't had a chance to look much yet.

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2011-01-13  8:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 15:23 [PATCH] radeonfb: Let hwmon driver probe the "monid" I2C bus Jean Delvare
2011-01-13  4:11 ` Paul Mundt
2011-01-13  4:44 ` Dave Airlie
2011-01-13  4:50 ` Benjamin Herrenschmidt
2011-01-13  8:22 ` Jean Delvare
2011-01-13  8:56 ` Jean Delvare [this message]
2011-02-02  5:50 ` Alexander Goomenyuk
2011-02-02  8:11 ` Jean Delvare
2011-02-02  8:12 ` Jean Delvare
2011-02-02  9:51 ` Benjamin Herrenschmidt
2011-02-02 10:00 ` Michel Dänzer
2011-02-03  5:41 ` Alexander Goomenyuk
2011-02-03  8:04 ` Jean Delvare

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=20110113095657.20b3f181@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=linux-fbdev@vger.kernel.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).