linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
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: Mon, 14 Jul 2003 22:11:43 +0200	[thread overview]
Message-ID: <20030714201143.GE902@elf.ucw.cz> (raw)
In-Reply-To: <1058200445.515.23.camel@gaston>

Hi!

> > > 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.
> > 
> > I believe it is bad idea to change driver
> > model again in 2.6.x-pre. I believe current
> > solution is pretty much okay.
> 
> Current solution is not okay and actually, the save_state/suspend
> distinction makes no sense. 
> We have designed a working solution
> a while ago now, Patrick has it implemented for month, it must
> get in now or 2.6 will not have proper power management but just
> "might work" kind of crap

save_state/suspend distinction may be irrelevant, but I don't see how
it makes whole current code "might work" kind of crap.

Can you describe some significant problem with current code? I do not
think it is good idea to have to touch all drivers in 2.6.0-test time
without some *good* reason.
								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2003-07-14 20:00 UTC|newest]

Thread overview: 8+ 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-09 11:35   ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-07-09 14:10     ` Russell King
2002-01-05 11:13       ` Pavel Machek
2003-07-14 16:34         ` Benjamin Herrenschmidt
2003-07-14 20:11           ` Pavel Machek [this message]
2003-07-09 17:45       ` James Simmons
2003-07-09 17:49         ` 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=20030714201143.GE902@elf.ucw.cz \
    --to=pavel@suse.cz \
    --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 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).