Bug 3128

Summary: Request to have i915 support backported for 6.8.3 release
Product: xorg Reporter: Matthias Saou <matthias>
Component: Driver/intelAssignee: Alan Hourihane <alanh>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: high CC: mharris
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Backport from current CVS
none
Backport from current CVS alanh: 6.8-branch?

Description Matthias Saou 2005-04-26 10:04:03 UTC 
Many new laptops (I don't know about desktops) are now coming with i915 graphic
chipsets, which don't work with 6.8.2's i810 driver, but work great with the
current CVS code.
I've tested it on my new laptop, it works great, and it was with Fedora Core 4
test 2 which already includes the i915 DRM kernel module, which also worked fine.

So I'd like to request to have backporting of the i915 support for the next Xorg
release be considered. If it doesn't involve too much complexity, of course.
Comment 1 Alan Hourihane 2005-07-04 12:37:46 UTC 
Marking as WONTFIX as there isn't going to be a 6.8.3 in the foreseeable future.

The 6.9/7.0 release is going to happen which will have the updated driver.
Comment 2 Alan Hourihane 2005-07-27 06:00:48 UTC 
I'm going to re-open this and mark it as a blocker for 6.8.3 so we can get the
patch in.
Comment 3 Alan Hourihane 2005-08-15 02:43:41 UTC 
Created attachment 2865 [details] [review]
Backport from current CVS

This gets the 6.8.2 driver up to speed with the current CVS, but should still
maintain compatibility with 6.8.2 for a 6.8.3 release.

Any problems - let me know.
Comment 4 Alan Hourihane 2005-08-15 02:47:44 UTC 
Created attachment 2866 [details] [review]
Backport from current CVS

Missed the i830_shadow.c (new file) in that last patch - use this instead.
Comment 5 Alan Hourihane 2006-05-02 21:31:42 UTC 
Closing. As 6.8.3 is unlikely to happen I suspect.

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.