On Fri, Nov 11, 2011 at 8:10 PM, Maarten Maathuis
wrote:
> On Fri, Nov 11, 2011 at 7:17 PM, James Simmons
> wrote:
>>
>>> On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
>>> > I'm not sure whether / how you handle the case of hardware render to
>>> > cursor surfaces on i915, b
On Fri, Nov 11, 2011 at 7:17 PM, James Simmons
wrote:
>
>> On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
>> > I'm not sure whether / how you handle the case of hardware render to
>> > cursor surfaces on i915, but it seems to me like if a lot of drivers
>> > need to implement d
> On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
> > I'm not sure whether / how you handle the case of hardware render to
> > cursor surfaces on i915, but it seems to me like if a lot of drivers
> > need to implement driver specific "tricks" to meet the semantics of
> > a generi
On Fri, Nov 11, 2011 at 8:10 PM, Maarten Maathuis wrote:
> On Fri, Nov 11, 2011 at 7:17 PM, James Simmons wrote:
>>
>>> On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
>>> > I'm not sure whether / how you handle the case of hardware render to
>>> > cursor surfaces on i915, but i
On Fri, Nov 11, 2011 at 7:17 PM, James Simmons wrote:
>
>> On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
>> > I'm not sure whether / how you handle the case of hardware render to
>> > cursor surfaces on i915, but it seems to me like if a lot of drivers
>> > need to implement dr
> On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
> > I'm not sure whether / how you handle the case of hardware render to
> > cursor surfaces on i915, but it seems to me like if a lot of drivers
> > need to implement driver specific "tricks" to meet the semantics of
> > a generi
On 11/05/2011 05:10 PM, Daniel Vetter wrote:
> On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
>
>> I'm not sure whether / how you handle the case of hardware render to
>> cursor surfaces on i915, but it seems to me like if a lot of drivers
>> need to implement driver specific
On 11/05/2011 05:10 PM, Daniel Vetter wrote:
On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
I'm not sure whether / how you handle the case of hardware render to
cursor surfaces on i915, but it seems to me like if a lot of drivers
need to implement driver specific "tricks"
On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
> I'm not sure whether / how you handle the case of hardware render to
> cursor surfaces on i915, but it seems to me like if a lot of drivers
> need to implement driver specific "tricks" to meet the semantics of
> a generic interface
On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
> I'm not sure whether / how you handle the case of hardware render to
> cursor surfaces on i915, but it seems to me like if a lot of drivers
> need to implement driver specific "tricks" to meet the semantics of
> a generic interface
On Fri, Nov 4, 2011 at 11:59 PM, Thomas Hellstrom
wrote:
> On 11/04/2011 11:49 PM, Maarten Maathuis wrote:
>>
>> On Fri, Nov 4, 2011 at 11:30 PM, Thomas Hellstrom
>> ?wrote:
>>
>>>
>>> On 11/04/2011 04:34 PM, Daniel Vetter wrote:
>>>
On Fri, Nov 04, 2011 at 12:59:59PM +0100, Thomas Hell
On 11/04/2011 11:49 PM, Maarten Maathuis wrote:
> On Fri, Nov 4, 2011 at 11:30 PM, Thomas Hellstrom
> wrote:
>
>> On 11/04/2011 04:34 PM, Daniel Vetter wrote:
>>
>>> On Fri, Nov 04, 2011 at 12:59:59PM +0100, Thomas Hellstrom wrote:
>>>
>>>
Hi.
I have a question ab
On Fri, Nov 4, 2011 at 11:30 PM, Thomas Hellstrom
wrote:
> On 11/04/2011 04:34 PM, Daniel Vetter wrote:
>>
>> On Fri, Nov 04, 2011 at 12:59:59PM +0100, Thomas Hellstrom wrote:
>>
>>>
>>> Hi.
>>>
>>> I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:
>>>
>>> Some hardware (v
On 11/04/2011 04:34 PM, Daniel Vetter wrote:
> On Fri, Nov 04, 2011 at 12:59:59PM +0100, Thomas Hellstrom wrote:
>
>> Hi.
>>
>> I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:
>>
>> Some hardware (vmware's virtual in particular) may not be able to
>> pick up the change
On Fri, Nov 04, 2011 at 12:59:59PM +0100, Thomas Hellstrom wrote:
> Hi.
>
> I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:
>
> Some hardware (vmware's virtual in particular) may not be able to
> pick up the changes from a bo directly, since the cursor data is
> sent tho
On Fri, Nov 4, 2011 at 11:59 PM, Thomas Hellstrom wrote:
> On 11/04/2011 11:49 PM, Maarten Maathuis wrote:
>>
>> On Fri, Nov 4, 2011 at 11:30 PM, Thomas Hellstrom
>> wrote:
>>
>>>
>>> On 11/04/2011 04:34 PM, Daniel Vetter wrote:
>>>
On Fri, Nov 04, 2011 at 12:59:59PM +0100, Thomas Hells
On 11/04/2011 11:49 PM, Maarten Maathuis wrote:
On Fri, Nov 4, 2011 at 11:30 PM, Thomas Hellstrom wrote:
On 11/04/2011 04:34 PM, Daniel Vetter wrote:
On Fri, Nov 04, 2011 at 12:59:59PM +0100, Thomas Hellstrom wrote:
Hi.
I have a question about the semantics of the DRM_IOCT
On Fri, Nov 4, 2011 at 11:30 PM, Thomas Hellstrom wrote:
> On 11/04/2011 04:34 PM, Daniel Vetter wrote:
>>
>> On Fri, Nov 04, 2011 at 12:59:59PM +0100, Thomas Hellstrom wrote:
>>
>>>
>>> Hi.
>>>
>>> I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:
>>>
>>> Some hardware (vm
On 11/04/2011 03:36 PM, Ilija Hadzic wrote:
>
>
> On Fri, 4 Nov 2011, Thomas Hellstrom wrote:
>
>> Hi.
>>
>> I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR
>> iotcl:
>>
>> Some hardware (vmware's virtual in particular) may not be able to
>> pick up the changes from a bo direct
On 11/04/2011 04:34 PM, Daniel Vetter wrote:
On Fri, Nov 04, 2011 at 12:59:59PM +0100, Thomas Hellstrom wrote:
Hi.
I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:
Some hardware (vmware's virtual in particular) may not be able to
pick up the changes from a bo direc
Hi.
I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:
Some hardware (vmware's virtual in particular) may not be able to pick
up the changes from a bo directly, since the cursor data is sent though
the command stream. Hence we need a notification when the cursor image
ha
On Fri, 4 Nov 2011, Thomas Hellstrom wrote:
> Hi.
>
> I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:
>
> Some hardware (vmware's virtual in particular) may not be able to pick up the
> changes from a bo directly, since the cursor data is sent though the command
> str
On Fri, Nov 04, 2011 at 12:59:59PM +0100, Thomas Hellstrom wrote:
> Hi.
>
> I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:
>
> Some hardware (vmware's virtual in particular) may not be able to
> pick up the changes from a bo directly, since the cursor data is
> sent tho
On 11/04/2011 03:36 PM, Ilija Hadzic wrote:
On Fri, 4 Nov 2011, Thomas Hellstrom wrote:
Hi.
I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR
iotcl:
Some hardware (vmware's virtual in particular) may not be able to
pick up the changes from a bo directly, since the cursor
On Fri, 4 Nov 2011, Thomas Hellstrom wrote:
Hi.
I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:
Some hardware (vmware's virtual in particular) may not be able to pick up the
changes from a bo directly, since the cursor data is sent though the command
stream. Hence
Hi.
I have a question about the semantics of the DRM_IOCTL_MODE_CURSOR iotcl:
Some hardware (vmware's virtual in particular) may not be able to pick
up the changes from a bo directly, since the cursor data is sent though
the command stream. Hence we need a notification when the cursor image
h
26 matches
Mail list logo