From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Karol Kozimor <sziwan@hell.org.pl>
Cc: Michael Frank <mhf@linuxmail.org>,
Micha Feigin <michf@post.tau.ac.il>,
Software suspend <swsusp-devel@lists.sourceforge.net>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] Re: Dropping CONFIG_PM_DISK?
Date: Mon, 01 Mar 2004 22:28:36 +1100 [thread overview]
Message-ID: <1078140515.21578.76.camel@gaston> (raw)
In-Reply-To: <20040301113528.GA21778@hell.org.pl>
On Mon, 2004-03-01 at 22:35, Karol Kozimor wrote:
> Thus wrote Benjamin Herrenschmidt:
> > > - that 2.4 style PM got depreciated and let die before the
> > > "new-driver-model" PM is workin
> > Except that it never worked
> > > - that perfectly good drivers were rewritten from scratch,
> > > but without functioning PM support
> > Please, give names.
>
> USB UHCI driver could be a fine example of a regression -- it could survive
> suspend in 2.4 under certain conditions, this is no longer true for 2.6.
Well, it may have survived by mere luck... the fact is that 2.4 never
had an infrastructure allowing anything remotely safe for
suspend/resume.
> There's also a great deal of people, who can't resume when AGP is being
> used -- that is again a regression over 2.4.
>
> The above are major showstoppers for most laptop users that already got
> used to stable and reliable swsusp and hence prefer to stick with 2.4.
There haven't been a regression in the AGP drivers themselves afaik.
Ben.
next prev parent reply other threads:[~2004-03-01 11:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1ulUA-33w-3@gated-at.bofh.it>
2004-02-29 16:17 ` Dropping CONFIG_PM_DISK? Karol Kozimor
2004-02-29 16:23 ` Pavel Machek
2004-02-29 17:32 ` Måns Rullgård
2004-02-29 18:10 ` Michael Frank
2004-02-29 21:33 ` [Swsusp-devel] " Micha Feigin
2004-03-01 2:51 ` Michael Frank
2004-03-01 11:09 ` Benjamin Herrenschmidt
2004-03-01 11:35 ` Karol Kozimor
2004-03-01 11:28 ` Benjamin Herrenschmidt [this message]
2004-03-01 11:51 ` Karol Kozimor
2004-03-01 12:56 ` Martin Wickman
2004-03-01 13:22 ` Michael Frank
2004-03-01 12:34 ` Micha Feigin
2004-03-01 11:31 ` Benjamin Herrenschmidt
2004-03-01 11:57 ` Karol Kozimor
2004-03-01 22:08 ` Benjamin Herrenschmidt
2004-03-01 11:43 ` Michael Frank
2004-03-01 11:39 ` Benjamin Herrenschmidt
2004-03-01 12:48 ` Michael Frank
2004-03-01 13:47 ` Arjan van de Ven
2004-03-01 14:33 ` Michael Frank
2004-03-01 14:38 ` Arjan van de Ven
2004-03-01 22:10 ` Benjamin Herrenschmidt
2004-02-29 18:10 ` Pavel Machek
2004-02-29 18:29 ` Måns Rullgård
2004-03-01 9:40 ` Pavel Machek
2004-03-01 10:08 ` Måns Rullgård
2004-03-01 10:39 ` Pavel Machek
2004-03-01 9:58 ` Nigel Cunningham
2004-03-01 12:46 ` Pavel Machek
2004-03-01 18:16 ` Nigel Cunningham
2004-03-01 20:22 ` Pavel Machek
2004-03-01 10:45 ` Michael Frank
2004-03-03 1:53 [Swsusp-devel] " John Mock
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=1078140515.21578.76.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.org \
--cc=michf@post.tau.ac.il \
--cc=swsusp-devel@lists.sourceforge.net \
--cc=sziwan@hell.org.pl \
/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