> > > 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?] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/