[Spice-devel] qxl X.org driver bo abstraction for user mode setting

[Dave Airlie]

On Wed, Feb 27, 2013 at 1:15 AM, Jeremy White <jwhite at codeweavers.com> wrote:
> Hey Dave,
>
> On 02/25/2013 10:32 PM, Dave Airlie wrote:
>> Hi,
>>
>> Okay this is the next chunk of prep for getting KMS into the driver,
>> the first 8 patches are just preparation work and moving stuff around,
>> along with a couple of minor fixes.
>>
>> The big guy on the end adds the BO abstraction layer, and makes all
>> the code use it, it doesn't contain any kms code, it prepares the way for it.
>>
>> I've probably broken xspice with this lot!
>
> I'm interested in tracking this to avoid that fate for xspice.  Can you
> give me a cluebat to 'bo abstraction' so I know what we're talking about?

Well it shouldn't change anything from Xspice execpt I broke the build
or something.

But essentially instead of having the core rendering routines in
UXA/surface code talk directly to the hardware, we introduce an
abstraction layer so the routines use generic buffer object based
interfaces. Then when I plug in KMS as a backend we don't have lots of
ugly ifdefs or hacks.

For Xspice using the UMS codepaths is always the right thing.

Dave.