From: "Martin Wickman" <martin.wickman@xms.se>
To: Karol Kozimor <sziwan@hell.org.pl>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
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 13:56:35 +0100 [thread overview]
Message-ID: <40433303.1020506@xms.se> (raw)
In-Reply-To: <20040301115135.GA2774@hell.org.pl>
Karol Kozimor wrote:
> Thus wrote Benjamin Herrenschmidt:
> Right, but the point is that while 2.6 has such an infrastructure, its
> introduction actually completely broke UHCI 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.
>>
>>There haven't been a regression in the AGP drivers themselves afaik.
>
> Which, again, leads us to conclusion that it was the driver model change
> that broke that.
>
> I'm not trying to criticize the driver model itself (I'm sure others have
> already done enough), but merely to emphasize that 2.6 is not yet ready for
> laptop users.
...and it's pretty obvious that it'll never be unless it's
fixed. Its kinda frustrating this agp resume thing keeps holding swsusp2
back -- everything else works (on my laptop at least).
next prev parent reply other threads:[~2004-03-01 12:56 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
2004-03-01 11:51 ` Karol Kozimor
2004-03-01 12:56 ` Martin Wickman [this message]
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=40433303.1020506@xms.se \
--to=martin.wickman@xms.se \
--cc=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