From: Russell King <rmk@arm.linux.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] fbdev and power management
Date: Wed, 9 Jul 2003 15:10:32 +0100 [thread overview]
Message-ID: <20030709151032.A22612@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1057750557.514.22.camel@gaston>; from benh@kernel.crashing.org on Wed, Jul 09, 2003 at 01:35:58PM +0200
On Wed, Jul 09, 2003 at 01:35:58PM +0200, Benjamin Herrenschmidt wrote:
> Note: The Power Management isn't well implemented in 2.5 yet. The
> infrastructure is mostly there, but the driver side semantics are
> still wrong. Patrick Mochel has a new implementation that is much
> better, but he didn't merge it upstream yet. I expect this will
> happen around Kernel Summit / OLS.
I'm slightly concerned by this. There are a growing amount of drivers
in 2.5 which are being made to work with the existing power management
system. This "new" system seems to have been hanging around for about
4 months now with no visible further work, presumably so that a paper
can be presented before its release.
My concern is that there has been:
- 4 months of non-exposure of this work
- 4 months of making the current system work
- and putting it in will require a fair number of drivers to be
re-worked.
Apart from driver re-work and that the core interfaces are supposed to
be stable, what are the technical arguments against merging it, say,
today?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-07-09 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030704042052.GL4359@himi.org>
2003-07-08 23:25 ` fbdev and power management James Simmons
2003-07-08 23:25 ` James Simmons
2003-07-09 11:35 ` Benjamin Herrenschmidt
2003-07-09 11:35 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-07-09 14:10 ` Russell King [this message]
2002-01-05 11:13 ` Pavel Machek
2002-01-05 11:13 ` [Linux-fbdev-devel] " Pavel Machek
2003-07-14 16:34 ` Benjamin Herrenschmidt
2003-07-14 16:34 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-07-14 20:11 ` Pavel Machek
2003-07-14 20:11 ` [Linux-fbdev-devel] " Pavel Machek
2003-07-09 17:45 ` James Simmons
2003-07-09 17:45 ` [Linux-fbdev-devel] " James Simmons
2003-07-09 17:49 ` Benjamin Herrenschmidt
2003-07-09 17:49 ` [Linux-fbdev-devel] " 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=20030709151032.A22612@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.