From: David Bronaugh <dbronaugh@linuxboxen.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Jon Smirl <jonsmirl@gmail.com>,
DRI Devel <dri-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: radeon-pre-2
Date: Mon, 13 Sep 2004 13:42:19 -0700 [thread overview]
Message-ID: <4146062B.8040603@linuxboxen.org> (raw)
In-Reply-To: <a728f9f9040913122160dd0134@mail.gmail.com>
Alex Deucher wrote:
>How would any of these plans handle power management and ACPI events?
>I'd like to be able to suspect my laptop with the DRI enabled, or have
>the DDX (or whatever) handle acpi lid and button events or put the
>chip into various power modes.
>
>Alex
>
>
Since I've been doing a little bit of ACPI hacking (and gained a bit of
understanding of it), I think I should probably speak on this one.
With the current ACPI infrastructure, you don't have the DDX or whatever
catching ACPI events -- acpid catches ACPI events, and does appropriate
things via scripts. So lid and button events can do things, but -- X
doesn't handle them. Scripts called by acpid do.
As to putting chips into various power modes -- wouldn't this be better
off in kernel, not in X? My impression is that this wouldn't be a large
amount of code. It could also abstract away some details of chip power
management -- it could (potentially) not matter if it's done via ACPI or
via a custom bit of code for a chip. And it could expose a file in sysfs
to adjust power settings for the graphics chip. Then the system that
exists for handling ACPI events can happily keep being how it is.
Yu, Luming has been doing a lot of work in the area of a generic ACPI
"video features" driver -- such a driver could do such things as change
which heads are enabled, set backlight power, and generally muck with
graphics state. I suspect some possible nasty interaction could happen,
since ACPI could affect graphics state in some pretty hairy ways. It
might be a good idea to get in contact with him before the user emails
show up...
David Bronaugh
ps: I kinda trimmed the CC: list on this
next prev parent reply other threads:[~2004-09-13 20:43 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E3389AF2-0272-11D9-A8D1-000A95F07A7A@fs.ei.tum.de>
[not found] ` <DA459966-02B9-11D9-A8D1-000A95F07A7A@fs.ei.tum.de>
[not found] ` <9e47339104090917353554a586@mail.gmail.com>
[not found] ` <Pine.LNX.4.58.0409100209100.32064@skynet>
[not found] ` <9e47339104090919015b5b5a4d@mail.gmail.com>
[not found] ` <20040910153135.4310c13a.felix@trabant>
[not found] ` <9e47339104091008115b821912@mail.gmail.com>
[not found] ` <1094829278.17801.18.camel@localhost.localdomain>
[not found] ` <9e4733910409100937126dc0e7@mail.gmail.com>
[not found] ` <1094832031.17883.1.camel@localhost.localdomain>
2004-09-10 17:22 ` radeon-pre-2 Jon Smirl
2004-09-10 17:04 ` radeon-pre-2 Alan Cox
2004-09-10 18:40 ` radeon-pre-2 Jon Smirl
2004-09-10 22:19 ` radeon-pre-2 Dave Airlie
2004-09-10 22:00 ` radeon-pre-2 Alan Cox
2004-09-10 23:24 ` radeon-pre-2 Dave Airlie
2004-09-11 7:40 ` radeon-pre-2 Geert Uytterhoeven
2004-09-11 8:42 ` radeon-pre-2 Keith Whitwell
2004-09-11 13:59 ` radeon-pre-2 Alan Cox
2004-09-11 0:47 ` radeon-pre-2 Vladimir Dergachev
2004-09-11 8:43 ` radeon-pre-2 Keith Whitwell
2004-09-11 12:23 ` radeon-pre-2 Mike Mestnik
2004-09-11 15:39 ` radeon-pre-2 Vladimir Dergachev
2004-09-11 14:14 ` radeon-pre-2 Alan Cox
2004-09-11 0:50 ` radeon-pre-2 Dave Airlie
2004-09-11 3:30 ` radeon-pre-2 Michel Dänzer
2004-09-11 5:19 ` radeon-pre-2 Dave Airlie
2004-09-11 6:12 ` radeon-pre-2 Michel Dänzer
2004-09-11 7:11 ` radeon-pre-2 Vladimir Dergachev
2004-09-11 14:36 ` radeon-pre-2 Alan Cox
2004-09-11 15:53 ` radeon-pre-2 Vladimir Dergachev
2004-09-11 15:14 ` radeon-pre-2 Alan Cox
2004-09-11 17:10 ` radeon-pre-2 Vladimir Dergachev
2004-09-11 16:20 ` radeon-pre-2 Alan Cox
2004-09-11 17:49 ` radeon-pre-2 Vladimir Dergachev
2004-09-11 17:59 ` radeon-pre-2 Jon Smirl
2004-09-11 18:05 ` radeon-pre-2 Vladimir Dergachev
2004-09-11 18:09 ` radeon-pre-2 Jon Smirl
2004-09-12 1:55 ` radeon-pre-2 Mike Mestnik
2004-09-11 9:20 ` radeon-pre-2 Antonino A. Daplas
2004-09-11 14:40 ` radeon-pre-2 Alan Cox
2004-09-11 16:34 ` radeon-pre-2 Jon Smirl
2004-09-11 14:33 ` radeon-pre-2 Alan Cox
2004-09-11 16:46 ` radeon-pre-2 Jon Smirl
2004-09-11 16:21 ` radeon-pre-2 Alan Cox
2004-09-11 17:27 ` radeon-pre-2 Jon Smirl
2004-09-13 11:40 ` radeon-pre-2 Keith Whitwell
2004-09-11 19:10 ` radeon-pre-2 Hamie
2004-09-11 23:20 ` radeon-pre-2 Alan Cox
2004-09-12 9:13 ` radeon-pre-2 Geert Uytterhoeven
2004-09-12 11:36 ` radeon-pre-2 Hamie
2004-09-12 17:31 ` radeon-pre-2 Alan Cox
2004-09-11 16:23 ` radeon-pre-2 Alan Cox
2004-09-11 14:25 ` radeon-pre-2 Alan Cox
2004-09-12 22:42 ` radeon-pre-2 Dave Airlie
2004-09-12 23:03 ` radeon-pre-2 Linus Torvalds
2004-09-13 0:27 ` radeon-pre-2 Michel Dänzer
2004-09-13 0:45 ` radeon-pre-2 Vladimir Dergachev
2004-09-13 0:52 ` radeon-pre-2 Michel Dänzer
2004-09-13 14:52 ` radeon-pre-2 Vladimir Dergachev
2004-09-13 13:57 ` radeon-pre-2 Alan Cox
2004-09-13 15:20 ` radeon-pre-2 Vladimir Dergachev
2004-09-13 15:07 ` radeon-pre-2 Alan Cox
2004-09-13 15:20 ` radeon-pre-2 Linus Torvalds
2004-09-13 19:21 ` radeon-pre-2 Alex Deucher
2004-09-13 20:42 ` David Bronaugh [this message]
2004-09-13 21:57 ` radeon-pre-2 Alex Deucher
2004-09-13 16:26 ` radeon-pre-2 Michel Dänzer
2004-09-13 6:05 ` radeon-pre-2 Alex Deucher
2004-09-13 16:29 ` radeon-pre-2 Michel Dänzer
2004-09-13 6:41 ` radeon-pre-2 Arjan van de Ven
2004-09-13 11:26 ` radeon-pre-2 Alan Cox
2004-09-13 15:06 ` radeon-pre-2 Jon Smirl
2004-09-13 15:04 ` radeon-pre-2 Alan Cox
2004-09-13 16:28 ` radeon-pre-2 Jon Smirl
2004-09-13 16:43 ` radeon-pre-2 Alan Cox
2004-09-13 18:11 ` radeon-pre-2 Jon Smirl
2004-09-13 18:49 ` radeon-pre-2 Jesse Barnes
2004-09-13 22:17 ` radeon-pre-2 Antonino A. Daplas
2004-09-13 17:50 ` radeon-pre-2 Jon Smirl
2004-09-14 10:27 ` radeon-pre-2 Alan Cox
2004-09-11 8:38 ` radeon-pre-2 Keith Whitwell
2004-09-10 23:10 ` radeon-pre-2 Jon Smirl
2004-09-10 22:17 ` radeon-pre-2 Alan Cox
2004-09-11 12:27 ` radeon-pre-2 Christoph Hellwig
2004-09-11 12:49 ` radeon-pre-2 Mike Mestnik
2004-09-11 16:45 ` radeon-pre-2 Christoph Hellwig
2004-09-11 16:11 ` radeon-pre-2 Jon Smirl
2004-09-11 16:45 ` radeon-pre-2 Christoph Hellwig
2004-09-11 17:02 ` radeon-pre-2 Linus Torvalds
2004-09-11 16:18 ` radeon-pre-2 Alan Cox
2004-09-11 17:49 ` radeon-pre-2 Linus Torvalds
2004-09-11 17:13 ` radeon-pre-2 Jon Smirl
2004-09-11 16:23 ` radeon-pre-2 Alan Cox
2004-09-11 17:41 ` radeon-pre-2 Linus Torvalds
2004-09-11 17:57 ` radeon-pre-2 Michel Dänzer
2004-09-11 20:29 ` radeon-pre-2 Eric Anholt
2004-09-11 21:41 ` radeon-pre-2 Jon Smirl
2004-09-11 17:54 ` radeon-pre-2 Jon Smirl
2004-09-11 18:13 ` radeon-pre-2 Linus Torvalds
2004-09-11 21:02 ` radeon-pre-2 Jon Smirl
2004-09-11 21:06 ` radeon-pre-2 Christoph Hellwig
2004-09-11 21:37 ` radeon-pre-2 Jon Smirl
2004-09-11 23:23 ` radeon-pre-2 Alan Cox
2004-09-12 7:12 ` radeon-pre-2 Eric Anholt
2004-09-12 0:21 ` radeon-pre-2 Jon Smirl
2004-09-12 0:28 ` radeon-pre-2 Linus Torvalds
2004-09-12 23:53 ` radeon-pre-2 Dave Airlie
2004-09-11 18:17 ` radeon-pre-2 Vladimir Dergachev
2004-09-10 17:12 ` radeon-pre-2 Alan Cox
[not found] ` <1094853894.18235.17.camel@localhost.localdomain>
2004-09-11 2:20 ` radeon-pre-2 Jon Smirl
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=4146062B.8040603@linuxboxen.org \
--to=dbronaugh@linuxboxen.org \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@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