Bug 333

Summary:	merge changes from DRI tree
Product:	xorg	Reporter:	Alex Deucher <alexdeucher>
Component:	Server/General	Assignee:	Eric Anholt <eta>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	high	CC:	ajax, dberger, petrosyan
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	269

Description Alex Deucher 2004-03-16 07:25:15 UTC

there are also quite a few new features in the DRI tree that could be
merged in at some point (not including the updated 3D drivers in mesa).  off the
top of my head:

- mergedfb support for radeon
- dri-interface changes
- configuration infrastructure
- fbconfig support
- dri support, lcd dpms support for savage

Comment 1 Eric Anholt 2004-06-14 12:46:51 UTC

I'm workign on this.

Comment 2 Eric Anholt 2004-06-16 03:43:41 UTC

All committed as far as I know, except for Mach64 and Savage DRI, due to
security issues.

Comment 3 OSavill 2004-06-18 05:25:13 UTC

Sorry to re-open this, but I have a Mach 64 chipset. What are the 'security
issues' ?? The package from the Retinal Burn and DRI SourceForge sites worked
just fine until a few XFree iterations ago. Then the compile still worked but
the XFree module fails to load due to unresolved references. But there is no
mention of 'security issues'. Please, please, please, pretty please, put in Mach
64 DRI stuff I am going through Tux Racer withdrawal symptoms !

Comment 4 Eric Anholt 2004-06-18 11:12:41 UTC

No, don't reopen it.  The Mach64 DRI *cannot* be merged, because it is
essentially a local root hole for anyone with access to the DRI device.  It's an
in-development driver suitable for testing on the machine that you're the only
user of (maybe), and you can get it using the DRI project's snapshots.

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.