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: Thu, 5 Sep 2002 21:29:08 -0600 [thread overview]
Message-ID: <20020906032912.16913.qmail@scrye.com> (raw)
In-Reply-To: 20020903093612.GC27884@dutidad.twi.tudelft.nl
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Charl" == Charl P Botha <c.p.botha-ra0OqMccq8edIhEUFHOBvg@public.gmane.org> writes:
Charl> Dear lists, Is anyone else using the new dri-resume
Charl> binaries/patches at http://cpbotha.net/dri_resume.html ? These
Charl> are different (read: improved) from the driReInit work in that
Charl> the new patches allow suspending/resuming whilst running 3D
Charl> applications.
Charl> I need some feedback, as one brave beta-tester is seeing
Charl> undefined symbols when building the modified radeon DRM and I
Charl> can't reproduce this problem on my systems.
Built fine here... Seems to have worked fine. I tried a swsusp and it
came back fine.
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.
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.
Happy to provide more info...
Charl> Thanks, 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/>
iD8DBQE9eCEH3imCezTjY0ERAjKHAJ0aLNzb2rFM1n7D7ssYZwPZrf/dDACfRFFI
1MO8Jwb6lyv53+KfiAUVeWM=
=daRD
-----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
next prev parent reply other threads:[~2002-09-06 3: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 [this message]
[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
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=20020906032912.16913.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