On Mon, Jun 23, 2014 at 10:45 AM, Maarten Lankhorst
wrote:
> But in drivers/drm I can encounter a similar issue, people expect to be able
> to
> overwrite the contents of the currently displayed buffer, so I 'solved' it by
> not adding
> a fence on the buffer, only by waiting for buffer idle
On Mon, Jun 23, 2014 at 10:45 AM, Maarten Lankhorst
maarten.lankho...@canonical.com wrote:
But in drivers/drm I can encounter a similar issue, people expect to be able
to
overwrite the contents of the currently displayed buffer, so I 'solved' it by
not adding
a fence on the buffer, only by
Hey,
op 20-06-14 22:52, Thierry Reding schreef:
> On Thu, Jun 19, 2014 at 02:28:14PM +0200, Daniel Vetter wrote:
>> On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
>> wrote:
> With these changes, can we pull the android sync logic out of
> drivers/staging/ now?
Afaik the google guys
Hey,
op 20-06-14 22:52, Thierry Reding schreef:
On Thu, Jun 19, 2014 at 02:28:14PM +0200, Daniel Vetter wrote:
On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
thierry.red...@gmail.com wrote:
With these changes, can we pull the android sync logic out of
drivers/staging/ now?
Afaik the google
On Thu, Jun 19, 2014 at 02:28:14PM +0200, Daniel Vetter wrote:
> On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
> wrote:
> >> > With these changes, can we pull the android sync logic out of
> >> > drivers/staging/ now?
> >>
> >> Afaik the google guys never really looked at this and acked it. So
On Thu, Jun 19, 2014 at 02:28:14PM +0200, Daniel Vetter wrote:
On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
thierry.red...@gmail.com wrote:
With these changes, can we pull the android sync logic out of
drivers/staging/ now?
Afaik the google guys never really looked at this and acked
On Thu, Jun 19, 2014 at 08:35:29AM -0700, Colin Cross wrote:
> On Thu, Jun 19, 2014 at 5:28 AM, Daniel Vetter wrote:
> > On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
> > wrote:
> >>> > With these changes, can we pull the android sync logic out of
> >>> > drivers/staging/ now?
> >>>
> >>>
op 19-06-14 17:22, Colin Cross schreef:
> On Wed, Jun 18, 2014 at 11:37 PM, Daniel Vetter wrote:
>> On Wed, Jun 18, 2014 at 06:15:56PM -0700, Greg KH wrote:
>>> On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
Just to show it's easy.
Android syncpoints can be
On Thu, Jun 19, 2014 at 5:28 AM, Daniel Vetter wrote:
> On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
> wrote:
>>> > With these changes, can we pull the android sync logic out of
>>> > drivers/staging/ now?
>>>
>>> Afaik the google guys never really looked at this and acked it. So I'm not
>>>
On Wed, Jun 18, 2014 at 11:37 PM, Daniel Vetter wrote:
> On Wed, Jun 18, 2014 at 06:15:56PM -0700, Greg KH wrote:
>> On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
>> > Just to show it's easy.
>> >
>> > Android syncpoints can be mapped to a timeline. This removes the need
>> >
On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
wrote:
>> > With these changes, can we pull the android sync logic out of
>> > drivers/staging/ now?
>>
>> Afaik the google guys never really looked at this and acked it. So I'm not
>> sure whether they'll follow along. The other issue I have as the
On Thu, Jun 19, 2014 at 08:37:27AM +0200, Daniel Vetter wrote:
> On Wed, Jun 18, 2014 at 06:15:56PM -0700, Greg KH wrote:
> > On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
> > > Just to show it's easy.
> > >
> > > Android syncpoints can be mapped to a timeline. This removes
On Wed, Jun 18, 2014 at 06:15:56PM -0700, Greg KH wrote:
> On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
> > Just to show it's easy.
> >
> > Android syncpoints can be mapped to a timeline. This removes the need
> > to maintain a separate api for synchronization. I've left the
On Wed, Jun 18, 2014 at 06:15:56PM -0700, Greg KH wrote:
On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
Just to show it's easy.
Android syncpoints can be mapped to a timeline. This removes the need
to maintain a separate api for synchronization. I've left the android
On Thu, Jun 19, 2014 at 08:37:27AM +0200, Daniel Vetter wrote:
On Wed, Jun 18, 2014 at 06:15:56PM -0700, Greg KH wrote:
On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
Just to show it's easy.
Android syncpoints can be mapped to a timeline. This removes the need
On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
thierry.red...@gmail.com wrote:
With these changes, can we pull the android sync logic out of
drivers/staging/ now?
Afaik the google guys never really looked at this and acked it. So I'm not
sure whether they'll follow along. The other issue I
On Wed, Jun 18, 2014 at 11:37 PM, Daniel Vetter dan...@ffwll.ch wrote:
On Wed, Jun 18, 2014 at 06:15:56PM -0700, Greg KH wrote:
On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
Just to show it's easy.
Android syncpoints can be mapped to a timeline. This removes the need
On Thu, Jun 19, 2014 at 5:28 AM, Daniel Vetter dan...@ffwll.ch wrote:
On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
thierry.red...@gmail.com wrote:
With these changes, can we pull the android sync logic out of
drivers/staging/ now?
Afaik the google guys never really looked at this and
op 19-06-14 17:22, Colin Cross schreef:
On Wed, Jun 18, 2014 at 11:37 PM, Daniel Vetter dan...@ffwll.ch wrote:
On Wed, Jun 18, 2014 at 06:15:56PM -0700, Greg KH wrote:
On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
Just to show it's easy.
Android syncpoints can be mapped
On Thu, Jun 19, 2014 at 08:35:29AM -0700, Colin Cross wrote:
On Thu, Jun 19, 2014 at 5:28 AM, Daniel Vetter dan...@ffwll.ch wrote:
On Thu, Jun 19, 2014 at 1:48 PM, Thierry Reding
thierry.red...@gmail.com wrote:
With these changes, can we pull the android sync logic out of
On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
> Just to show it's easy.
>
> Android syncpoints can be mapped to a timeline. This removes the need
> to maintain a separate api for synchronization. I've left the android
> trace events in place, but the core fence events should
Just to show it's easy.
Android syncpoints can be mapped to a timeline. This removes the need
to maintain a separate api for synchronization. I've left the android
trace events in place, but the core fence events should already be
sufficient for debugging.
v2:
- Call fence_remove_callback in
Just to show it's easy.
Android syncpoints can be mapped to a timeline. This removes the need
to maintain a separate api for synchronization. I've left the android
trace events in place, but the core fence events should already be
sufficient for debugging.
v2:
- Call fence_remove_callback in
On Wed, Jun 18, 2014 at 12:37:11PM +0200, Maarten Lankhorst wrote:
Just to show it's easy.
Android syncpoints can be mapped to a timeline. This removes the need
to maintain a separate api for synchronization. I've left the android
trace events in place, but the core fence events should
24 matches
Mail list logo