Bug 3496

Summary:	Driver claims to need DRM 1.2.0 for suspend, but works with 1.1.0
Product:	xorg	Reporter:	Daniel Stone <daniel>
Component:	Driver/intel	Assignee:	Alan Hourihane <alanh>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	normal
Priority:	high
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description FreeDesktop Bugzilla Database Corruption Fix User 2005-06-08 11:40:03 UTC

The i830 driver will happily survive a suspend/resume cycle using the DRM driver
in current kernels, which claims to be 1.1.0. However, the code checks for 1.2.0
and fails. Modifying the DRM driver to report itself as 1.2.0 results in correct
behaviour.

Comment 1 Alan Hourihane 2005-06-08 12:13:08 UTC

The driver does need v1.2 for suspend/resume to work for 3D applications. You'll
notice if you are using v1.1 then 3D applications will not work when you have
resumed.

This is not a bug.

Comment 2 FreeDesktop Bugzilla Database Corruption Fix User 2005-06-08 12:20:24 UTC

I have working 3D over suspend/resume using the code currently in the Linux
kernel (2.6.12-rc5), which before patching claims to be version 1.1.0. Looking
at diffs between that and the DRM code in xorg cvs, I can't find any code that's
relevant to this functionality.

Comment 3 Alan Hourihane 2005-06-08 12:21:04 UTC

Ugh, it appears something got screwed on the import to the kernel as it's got
the code to support resume but someone didn't bump the version.

I'll get this corrected in the kernel.

Comment 4 Alan Hourihane 2005-06-09 02:24:11 UTC

My fault, it appears that the initial commit of the DRM code was not bumped to
1.2 correctly. And seeing as X.Org hasn't released a version with resume
functionality yet, it's easier to remove the check from the X tree.

I'll commit the change to do this now.

Comment 5 FreeDesktop Bugzilla Database Corruption Fix User 2005-06-09 02:32:45 UTC

Wonderful, thanks!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.