Backing out DRI2 from server 1.5

[Dave Airlie]

On Tue, Aug 5, 2008 at 5:39 PM, Alan Hourihane <alanh at fairlite.co.uk> wrote:
> On Mon, 2008-08-04 at 17:20 -0400, Kristian Høgsberg wrote:
>> Hi,
>>
>> Since it looks like we'll be going with GEM for the memory manager,
>> I'll have to revisit some of the DRI2 design decisions.  As a first
>> step, I want to back out the DRI2 stuff from the 1.5 X server
>> entirely, since it uses TTM API for creating and mapping the DRI2
>> sarea.  We're in feature freeze with 1.5 and I won't be able to update
>> it in time anyway, so the best option is to just back it out instead
>> of releasing a server with modules expecting an API that was never
>> released.
>
> GEM is currently Intel specific.
>
> It seems as though the memory managers are going to be driver specific
> at this time, so we can't have the Xserver relying on a specific one.
>
> Maybe we should have some callbacks to the driver for DRI2 specific
> handling ?
>

I think that is the current plan, the shared area for DRI2 will be an
shm object independent of memory manager.

everything else will be 32-bit handles.

Dave.