From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.redhat.com
Subject: Re: swsusp / 2.6.0-test1
Date: Tue, 22 Jul 2003 00:45:41 +0300 [thread overview]
Message-ID: <3F1C5F05.5030903@kolumbus.fi> (raw)
In-Reply-To: 20030721213141.GF436@elf.ucw.cz
Pavel Machek wrote:
>Hi!
>
>
>
>>>>swsusp is working fine, but mplayer
>>>>in sdl and xv output mode displays a blank
>>>>screen after a resume.
>>>>
>>>>
>>>>
>>>You probably need to write suspend/resume support for your card.
>>>
>>>
>>>
>>Just wondering what kind of support for suspend/resume is "enough", say
>>for video cards? Surely not the pci configuration space, you need to
>>restore video mode, color maps, gfx engine state etc etc...what about
>>frame buffer contents on card? Probably yes. Sounds like a lot of code,
>>and different thing for every possible video card. Is there some general
>>guidance here? Is drivers/video soon bloating with tons of
>>suspend/resume code? I hope I am wrong :)
>>
>>
>
>I'm not sure if you are wrong. If you switch to non-graphics console,
>that may save some code, but...
>
>
>
ah ok, so at this stage swsuspending a X desktop doesn't work in general
case, of course depending on video hardware? If X had some notion of
suspend/resume things would be easier, than insisting every single
driver save and restore all. After all the pci config space should be
enough for kernel drivers?
>BTW vger.redhat.com, what is that?
> Pavel
>
Don't know, just did reply all and seems to work :)
--Mika
next prev parent reply other threads:[~2003-07-21 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 16:38 swsusp / 2.6.0-test1 Andreas Jellinghaus
2003-07-21 16:48 ` Andreas Jellinghaus
2003-07-21 19:36 ` Pavel Machek
2003-07-21 21:33 ` Mika Penttilä
2003-07-21 21:31 ` Pavel Machek
2003-07-21 21:45 ` Mika Penttilä [this message]
2003-07-21 21:44 ` Pavel Machek
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=3F1C5F05.5030903@kolumbus.fi \
--to=mika.penttila@kolumbus.fi \
--cc=linux-kernel@vger.redhat.com \
--cc=pavel@suse.cz \
/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).