From: Kevin Fenzi <kevin-acpi-+bl/7iUgRMUAvxtiuMwx3w@public.gmane.org>
To: "Charl P. Botha" <c.p.botha-ra0OqMccq8edIhEUFHOBvg@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: dri-resume XFree86
Date: Fri, 6 Sep 2002 09:29:08 -0600 [thread overview]
Message-ID: <20020906152912.4665.qmail@scrye.com> (raw)
In-Reply-To: <20020906074200.GA26504-V1rPnKwUOrA59+mn7qD7y50iERQUc4G+@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Charl" == Charl P Botha <c.p.botha-ra0OqMccq8edIhEUFHOBvg@public.gmane.org> writes:
Charl> On Thu, Sep 05, 2002 at 09:29:08PM -0600, Kevin Fenzi wrote:
>> Built fine here... Seems to have worked fine. I tried a swsusp and
>> it came back fine.
Charl> Whoop!
>> You might note that you no longer need to abort the suspend if your
>> radeon module is still in use. At least it worked for me with it
>> still in use... and it never was not in use.
Charl> I made the new modifications to do specifically this... X never
Charl> releases its handle on the DRM. The "old" way (which does have
Charl> some other applications) could break severely if it released
Charl> the DRM whilst for instance a Qt app was running. So, in
Charl> short, with the new patch you can just suspend/resume at your
Charl> heart's content, even while a 3D app or somesuch is running.
excellent. ;)
might make a 'README.upgradingfromKludge'
I was thinking for a few seconds that it had broken swsusp entirely,
but it turns out I had a check in there that if radeon was in use it
should abort. ;)
>> One other strange thing... after a swsusp everything comes back
>> except Xv does look like it works. It just gives a blank window for
>> anything that uses Xv. :( This was the case with the driReInit
>> version as well. Or the stock X modules/libs.
Charl> Durn. I haven't even started looking at this. So after a
Charl> resume, there's no way of getting Xv going again short of
Charl> restarting X?
yep. If I start another X server it works fine, or restart that one,
but in the one that was going over the suspend it doesn't work.
No errors, and it seems to detect it like it's still there, but it
doesn't display anything.
>> Happy to provide more info...
Charl> Thanks very much for testing!
anytime.
Charl> Regards, Charl
kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard <http://www.gnupg.org/>
iD8DBQE9eMnI3imCezTjY0ERAq1xAJsFz39BPlawqo4UK4kDmEpqJyoGGgCfQG7E
/wetosOUhmLPRSLxbLPM9Ws=
=+VPS
-----END PGP SIGNATURE-----
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
prev parent reply other threads:[~2002-09-06 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 9:36 dri-resume XFree86 Charl P. Botha
2002-09-06 3:29 ` Kevin Fenzi
[not found] ` <20020906032912.16913.qmail-+bl/7iUgRMUAvxtiuMwx3w@public.gmane.org>
2002-09-06 7:42 ` Charl P. Botha
[not found] ` <20020906074200.GA26504-V1rPnKwUOrA59+mn7qD7y50iERQUc4G+@public.gmane.org>
2002-09-06 15:29 ` Kevin Fenzi [this message]
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=20020906152912.4665.qmail@scrye.com \
--to=kevin-acpi-+bl/7iugrmuavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=c.p.botha-ra0OqMccq8edIhEUFHOBvg@public.gmane.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