From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Daniël Mantione" <daniel@deadlock.et.tudelft.nl>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>,
James Simmons <jsimmons@infradead.org>
Subject: Re: Patch: Make iBook1 work again
Date: Fri, 19 Sep 2003 09:40:48 +0200 [thread overview]
Message-ID: <1063957248.603.38.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0309190902480.17132-100000@deadlock.et.tudelft.nl>
> Indeed, we cannot change clocks because of results of only one machine. It
> just makes me wonder. Perhaps the best thing to do is to check this with
> ATi too.
I need a brown paper bag here. A while ago (maybe 3 years), ATI send me
a list of RefClk/MCLK/XCLK for their entire line of Mac chips with the
Open Firmware node name so we could identify them. Some way, I lost that
list (disk crash)... It was covering all "Mac" mach64 boards and a bunch
of the r128 ones iirc. We don't need that as badly on recent machines as
recent ATI cards provide the RefClk in the device-tree and we don't need
to mess with the MLCK/XCLK any more on radeons.
> Okay.... By the way, how shall we get the powermanagement code to work on
> x86? As far as I saw that register backlight procedure exists only on PowerPC.
The backlight "core" is a simple thing I did for PowerBook (since the
backlight can be either done by the ATI chip or by some other uController
on the motherboard). This current implementation is only suitable for
a single panel and isn't something worth extending I beleive.
Better would be to add proper backlight/frontlight/contrast control to
2.6 via the generic monitor infrastructure, maybe via sysfs. This covers
more than just laptops: Flat panels on ADC/DVI can have USB controlled
backlight, things like CRT iMacs have a chip that allow to control
brightness & all of the geometry settings via i2c etc... We would need
a common interface to userland for these at least, even if the actual
implementation in the drivers is full of platform specific hooks, there
is not much we can do about it for now I'm afraid.
The sleep code is something specific to the way those chips are put
to sleep on Macs. AFAIK, their clock is removed but not their power.
I don't know if that can be useful on any x86 laptop...
Ben.
next prev parent reply other threads:[~2003-09-19 7:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0309162303490.32610-100000@deadlock.et.tudelft.nl>
2003-09-17 20:07 ` Patch: Make iBook1 work again Benjamin Herrenschmidt
2003-09-17 20:42 ` Daniël Mantione
2003-09-17 21:12 ` Benjamin Herrenschmidt
2003-09-17 21:10 ` Daniël Mantione
2003-09-17 21:23 ` Benjamin Herrenschmidt
2003-09-17 21:49 ` Daniël Mantione
2003-09-18 8:00 ` Daniël Mantione
2003-09-18 9:03 ` Benjamin Herrenschmidt
2003-09-18 20:23 ` Benjamin Herrenschmidt
2003-09-18 22:06 ` Daniël Mantione
2003-09-19 6:57 ` Benjamin Herrenschmidt
2003-09-19 7:09 ` Daniël Mantione
2003-09-19 7:40 ` Benjamin Herrenschmidt [this message]
2003-09-19 8:29 ` Daniël Mantione
2003-09-19 8:38 ` Benjamin Herrenschmidt
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=1063957248.603.38.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=daniel@deadlock.et.tudelft.nl \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com.br \
/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