On Mon, Apr 4, 2016 at 11:41 AM, Rob Clark wrote:
> On Sun, Apr 3, 2016 at 8:14 PM, Inki Dae wrote:
>>
>> 2016년 03월 31일 23:10에 Rob Clark 이(가) 쓴 글:
>>> On Thu, Mar 31, 2016 at 7:26 AM, Inki Dae wrote:
Hi Daniel,
On Mon, Apr 4, 2016 at 11:41 AM, Rob Clark wrote:
> On Sun, Apr 3, 2016 at 8:14 PM, Inki Dae wrote:
>>
>> 2016년 03월 31일 23:10에 Rob Clark 이(가) 쓴 글:
>>> On Thu, Mar 31, 2016 at 7:26 AM, Inki Dae wrote:
Hi Daniel,
2016-03-31 19:56 GMT+09:00 Daniel Stone :
> Hi Inki,
>
>
On Sun, Apr 3, 2016 at 8:14 PM, Inki Dae wrote:
>
> 2016년 03월 31일 23:10에 Rob Clark 이(가) 쓴 글:
>> On Thu, Mar 31, 2016 at 7:26 AM, Inki Dae wrote:
>>> Hi Daniel,
>>>
>>> 2016-03-31 19:56 GMT+09:00 Daniel Stone :
Hi Inki,
On Sun, Apr 3, 2016 at 8:14 PM, Inki Dae wrote:
>
> 2016년 03월 31일 23:10에 Rob Clark 이(가) 쓴 글:
>> On Thu, Mar 31, 2016 at 7:26 AM, Inki Dae wrote:
>>> Hi Daniel,
>>>
>>> 2016-03-31 19:56 GMT+09:00 Daniel Stone :
Hi Inki,
On 31 March 2016 at 11:05, Inki Dae wrote:
> 2016년 03월
2016년 03월 31일 23:10에 Rob Clark 이(가) 쓴 글:
> On Thu, Mar 31, 2016 at 7:26 AM, Inki Dae wrote:
>> Hi Daniel,
>>
>> 2016-03-31 19:56 GMT+09:00 Daniel Stone :
>>> Hi Inki,
>>>
>>> On 31 March 2016 at 11:05, Inki Dae wrote:
2016년 03월
2016년 03월 31일 23:10에 Rob Clark 이(가) 쓴 글:
> On Thu, Mar 31, 2016 at 7:26 AM, Inki Dae wrote:
>> Hi Daniel,
>>
>> 2016-03-31 19:56 GMT+09:00 Daniel Stone :
>>> Hi Inki,
>>>
>>> On 31 March 2016 at 11:05, Inki Dae wrote:
2016년 03월 31일 18:35에 Daniel Stone 이(가) 쓴 글:
> On 31 March 2016 at
On Thu, Mar 31, 2016 at 7:26 AM, Inki Dae wrote:
> Hi Daniel,
>
> 2016-03-31 19:56 GMT+09:00 Daniel Stone :
>> Hi Inki,
>>
>> On 31 March 2016 at 11:05, Inki Dae wrote:
>>> 2016년 03월 31일 18:35에 Daniel Stone 이(가) 쓴 글:
On 31 March
On Thu, Mar 31, 2016 at 7:26 AM, Inki Dae wrote:
> Hi Daniel,
>
> 2016-03-31 19:56 GMT+09:00 Daniel Stone :
>> Hi Inki,
>>
>> On 31 March 2016 at 11:05, Inki Dae wrote:
>>> 2016년 03월 31일 18:35에 Daniel Stone 이(가) 쓴 글:
On 31 March 2016 at 08:45, Inki Dae wrote:
> As of now, it seems that
Hi Inki,
On 31 March 2016 at 12:26, Inki Dae wrote:
> 2016-03-31 19:56 GMT+09:00 Daniel Stone :
>> On 31 March 2016 at 11:05, Inki Dae wrote:
>>> Then, existing drivers would need additional works for explicit fencing
>>> support.
Hi Inki,
On 31 March 2016 at 12:26, Inki Dae wrote:
> 2016-03-31 19:56 GMT+09:00 Daniel Stone :
>> On 31 March 2016 at 11:05, Inki Dae wrote:
>>> Then, existing drivers would need additional works for explicit fencing
>>> support. This wouldn't be really what the drivers have to but should be
2016-03-31 19:04 GMT+09:00 Daniel Vetter :
> On Thu, Mar 31, 2016 at 10:35:11AM +0100, Daniel Stone wrote:
>> Well, it has to be one or the other: mixing explicit and implicit,
>> defeats the purpose of using explicit fencing. So, when explicit
>> fencing is in use, implicit
2016-03-31 19:04 GMT+09:00 Daniel Vetter :
> On Thu, Mar 31, 2016 at 10:35:11AM +0100, Daniel Stone wrote:
>> Well, it has to be one or the other: mixing explicit and implicit,
>> defeats the purpose of using explicit fencing. So, when explicit
>> fencing is in use, implicit fences must be
Hi Daniel,
2016-03-31 19:56 GMT+09:00 Daniel Stone :
> Hi Inki,
>
> On 31 March 2016 at 11:05, Inki Dae wrote:
>> 2016년 03월 31일 18:35에 Daniel Stone 이(가) 쓴 글:
>>> On 31 March 2016 at 08:45, Inki Dae wrote:
As of now, it seems
Hi Daniel,
2016-03-31 19:56 GMT+09:00 Daniel Stone :
> Hi Inki,
>
> On 31 March 2016 at 11:05, Inki Dae wrote:
>> 2016년 03월 31일 18:35에 Daniel Stone 이(가) 쓴 글:
>>> On 31 March 2016 at 08:45, Inki Dae wrote:
As of now, it seems that this wouldn't be optional but mandatory if
explicit
Hi Inki,
On 31 March 2016 at 11:05, Inki Dae wrote:
> 2016년 03월 31일 18:35에 Daniel Stone 이(가) 쓴 글:
>> On 31 March 2016 at 08:45, Inki Dae wrote:
>>> As of now, it seems that this wouldn't be optional but mandatory if
>>> explicit fence support is
Hi Inki,
On 31 March 2016 at 11:05, Inki Dae wrote:
> 2016년 03월 31일 18:35에 Daniel Stone 이(가) 쓴 글:
>> On 31 March 2016 at 08:45, Inki Dae wrote:
>>> As of now, it seems that this wouldn't be optional but mandatory if
>>> explicit fence support is added to the atomic helper framework. This would
Hi Daniel,
2016년 03월 31일 18:35에 Daniel Stone 이(가) 쓴 글:
> Hi Inki,
>
> On 31 March 2016 at 08:45, Inki Dae wrote:
>> 2016년 03월 29일 22:23에 Rob Clark 이(가) 쓴 글:
>>> On Mon, Mar 28, 2016 at 10:18 PM, Inki Dae wrote:
In addition, I wonder how explicit
Hi Daniel,
2016년 03월 31일 18:35에 Daniel Stone 이(가) 쓴 글:
> Hi Inki,
>
> On 31 March 2016 at 08:45, Inki Dae wrote:
>> 2016년 03월 29일 22:23에 Rob Clark 이(가) 쓴 글:
>>> On Mon, Mar 28, 2016 at 10:18 PM, Inki Dae wrote:
In addition, I wonder how explicit and implicit fences could coexist
On Thu, Mar 31, 2016 at 10:35:11AM +0100, Daniel Stone wrote:
> Well, it has to be one or the other: mixing explicit and implicit,
> defeats the purpose of using explicit fencing. So, when explicit
> fencing is in use, implicit fences must be ignored.
You can mix it, if you're careful. CrOS wants
On Thu, Mar 31, 2016 at 10:35:11AM +0100, Daniel Stone wrote:
> Well, it has to be one or the other: mixing explicit and implicit,
> defeats the purpose of using explicit fencing. So, when explicit
> fencing is in use, implicit fences must be ignored.
You can mix it, if you're careful. CrOS wants
Hi Inki,
On 31 March 2016 at 08:45, Inki Dae wrote:
> 2016년 03월 29일 22:23에 Rob Clark 이(가) 쓴 글:
>> On Mon, Mar 28, 2016 at 10:18 PM, Inki Dae wrote:
>>> In addition, I wonder how explicit and implicit fences could coexist
>>> together.
>>> Rob said,
Hi Inki,
On 31 March 2016 at 08:45, Inki Dae wrote:
> 2016년 03월 29일 22:23에 Rob Clark 이(가) 쓴 글:
>> On Mon, Mar 28, 2016 at 10:18 PM, Inki Dae wrote:
>>> In addition, I wonder how explicit and implicit fences could coexist
>>> together.
>>> Rob said,
>>> "Implicit sync ofc remains the default,
2016년 03월 29일 22:23에 Rob Clark 이(가) 쓴 글:
> On Mon, Mar 28, 2016 at 10:18 PM, Inki Dae wrote:
>>
>> In addition, I wonder how explicit and implicit fences could coexist
>> together.
>> Rob said,
>> "Implicit sync ofc remains the default, but userspace could opt-in to
>>
2016년 03월 29일 22:23에 Rob Clark 이(가) 쓴 글:
> On Mon, Mar 28, 2016 at 10:18 PM, Inki Dae wrote:
>>
>> In addition, I wonder how explicit and implicit fences could coexist
>> together.
>> Rob said,
>> "Implicit sync ofc remains the default, but userspace could opt-in to
>> explicit sync instead"
On Mon, Mar 28, 2016 at 10:18 PM, Inki Dae wrote:
>
> In addition, I wonder how explicit and implicit fences could coexist together.
> Rob said,
> "Implicit sync ofc remains the default, but userspace could opt-in to
> explicit sync instead"
>
> This would mean that if we
On Mon, Mar 28, 2016 at 10:18 PM, Inki Dae wrote:
>
> In addition, I wonder how explicit and implicit fences could coexist together.
> Rob said,
> "Implicit sync ofc remains the default, but userspace could opt-in to
> explicit sync instead"
>
> This would mean that if we use explicit sync for
Hi Daniel,
2016년 03월 28일 22:26에 Daniel Stone 이(가) 쓴 글:
> Hi Inki,
>
> On 28 March 2016 at 02:26, Inki Dae wrote:
>> 2016년 03월 25일 21:10에 Daniel Stone 이(가) 쓴 글:
>>> Second, really. Vulkan avoids implicit sync entirely, and exposes
>>> fence-like primitives throughout its
Hi Daniel,
2016년 03월 28일 22:26에 Daniel Stone 이(가) 쓴 글:
> Hi Inki,
>
> On 28 March 2016 at 02:26, Inki Dae wrote:
>> 2016년 03월 25일 21:10에 Daniel Stone 이(가) 쓴 글:
>>> Second, really. Vulkan avoids implicit sync entirely, and exposes
>>> fence-like primitives throughout its whole API. These include
Hi Inki,
On 28 March 2016 at 02:26, Inki Dae wrote:
> 2016년 03월 25일 21:10에 Daniel Stone 이(가) 쓴 글:
>> Second, really. Vulkan avoids implicit sync entirely, and exposes
>> fence-like primitives throughout its whole API. These include being
>> able to pass prerequisite fences
Hi Inki,
On 28 March 2016 at 02:26, Inki Dae wrote:
> 2016년 03월 25일 21:10에 Daniel Stone 이(가) 쓴 글:
>> Second, really. Vulkan avoids implicit sync entirely, and exposes
>> fence-like primitives throughout its whole API. These include being
>> able to pass prerequisite fences for display (what
Hi Rob and Daniel,
2016년 03월 25일 21:10에 Daniel Stone 이(가) 쓴 글:
> Hi all,
>
> On 25 March 2016 at 11:58, Rob Clark wrote:
>> On Thu, Mar 24, 2016 at 7:49 PM, Inki Dae wrote:
>>> It's definitely different case. This tries to add new user-space
Hi Rob and Daniel,
2016년 03월 25일 21:10에 Daniel Stone 이(가) 쓴 글:
> Hi all,
>
> On 25 March 2016 at 11:58, Rob Clark wrote:
>> On Thu, Mar 24, 2016 at 7:49 PM, Inki Dae wrote:
>>> It's definitely different case. This tries to add new user-space interfaces
>>> to expose fences to user-space. At
Hi all,
On 25 March 2016 at 11:58, Rob Clark wrote:
> On Thu, Mar 24, 2016 at 7:49 PM, Inki Dae wrote:
>> It's definitely different case. This tries to add new user-space interfaces
>> to expose fences to user-space. At least, implicit interfaces are
Hi all,
On 25 March 2016 at 11:58, Rob Clark wrote:
> On Thu, Mar 24, 2016 at 7:49 PM, Inki Dae wrote:
>> It's definitely different case. This tries to add new user-space interfaces
>> to expose fences to user-space. At least, implicit interfaces are embedded
>> into drivers.
>> So I'd like
On Thu, Mar 24, 2016 at 7:49 PM, Inki Dae wrote:
>
>
> 2016년 03월 25일 00:40에 Rob Clark 이(가) 쓴 글:
>> On Thu, Mar 24, 2016 at 4:18 AM, Inki Dae wrote:
>>> Hi,
>>>
>>> 2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
From: Gustavo Padovan
On Thu, Mar 24, 2016 at 7:49 PM, Inki Dae wrote:
>
>
> 2016년 03월 25일 00:40에 Rob Clark 이(가) 쓴 글:
>> On Thu, Mar 24, 2016 at 4:18 AM, Inki Dae wrote:
>>> Hi,
>>>
>>> 2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
From: Gustavo Padovan
Hi,
This is a first proposal to
2016년 03월 25일 00:40에 Rob Clark 이(가) 쓴 글:
> On Thu, Mar 24, 2016 at 4:18 AM, Inki Dae wrote:
>> Hi,
>>
>> 2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
>>> From: Gustavo Padovan
>>>
>>> Hi,
>>>
>>> This is a first proposal to discuss the
2016년 03월 25일 00:40에 Rob Clark 이(가) 쓴 글:
> On Thu, Mar 24, 2016 at 4:18 AM, Inki Dae wrote:
>> Hi,
>>
>> 2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
>>> From: Gustavo Padovan
>>>
>>> Hi,
>>>
>>> This is a first proposal to discuss the addition of in-fences support
>>> to DRM. It adds a new
Hi Guestavo,
2016년 03월 24일 23:39에 Gustavo Padovan 이(가) 쓴 글:
> Hi Inki,
>
> 2016-03-24 Inki Dae :
>
>> Hi,
>>
>> 2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
>>> From: Gustavo Padovan
>>>
>>> Hi,
>>>
>>> This is a first proposal to
Hi Guestavo,
2016년 03월 24일 23:39에 Gustavo Padovan 이(가) 쓴 글:
> Hi Inki,
>
> 2016-03-24 Inki Dae :
>
>> Hi,
>>
>> 2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
>>> From: Gustavo Padovan
>>>
>>> Hi,
>>>
>>> This is a first proposal to discuss the addition of in-fences support
>>> to DRM. It adds
On Thu, Mar 24, 2016 at 4:18 AM, Inki Dae wrote:
> Hi,
>
> 2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
>> From: Gustavo Padovan
>>
>> Hi,
>>
>> This is a first proposal to discuss the addition of in-fences support
>> to DRM. It adds a new
On Thu, Mar 24, 2016 at 4:18 AM, Inki Dae wrote:
> Hi,
>
> 2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
>> From: Gustavo Padovan
>>
>> Hi,
>>
>> This is a first proposal to discuss the addition of in-fences support
>> to DRM. It adds a new struct to fence.c to abstract the use of sync_file
>>
Hi Inki,
2016-03-24 Inki Dae :
> Hi,
>
> 2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
> > From: Gustavo Padovan
> >
> > Hi,
> >
> > This is a first proposal to discuss the addition of in-fences support
> > to DRM. It adds a new struct to
Hi Inki,
2016-03-24 Inki Dae :
> Hi,
>
> 2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
> > From: Gustavo Padovan
> >
> > Hi,
> >
> > This is a first proposal to discuss the addition of in-fences support
> > to DRM. It adds a new struct to fence.c to abstract the use of sync_file
> > in DRM
Hi Maarten,
2016-03-24 Maarten Lankhorst :
> Hey,
>
> Op 23-03-16 om 19:47 schreef Gustavo Padovan:
> > From: Gustavo Padovan
> >
> > Hi,
> >
> > This is a first proposal to discuss the addition of in-fences support
> > to
Hi Maarten,
2016-03-24 Maarten Lankhorst :
> Hey,
>
> Op 23-03-16 om 19:47 schreef Gustavo Padovan:
> > From: Gustavo Padovan
> >
> > Hi,
> >
> > This is a first proposal to discuss the addition of in-fences support
> > to DRM. It adds a new struct to fence.c to abstract the use of sync_file
>
Hi,
2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
> From: Gustavo Padovan
>
> Hi,
>
> This is a first proposal to discuss the addition of in-fences support
> to DRM. It adds a new struct to fence.c to abstract the use of sync_file
> in DRM drivers. The new
Hi,
2016년 03월 24일 03:47에 Gustavo Padovan 이(가) 쓴 글:
> From: Gustavo Padovan
>
> Hi,
>
> This is a first proposal to discuss the addition of in-fences support
> to DRM. It adds a new struct to fence.c to abstract the use of sync_file
> in DRM drivers. The new struct fence_collection contains a
Hey,
Op 23-03-16 om 19:47 schreef Gustavo Padovan:
> From: Gustavo Padovan
>
> Hi,
>
> This is a first proposal to discuss the addition of in-fences support
> to DRM. It adds a new struct to fence.c to abstract the use of sync_file
> in DRM drivers. The new
Hey,
Op 23-03-16 om 19:47 schreef Gustavo Padovan:
> From: Gustavo Padovan
>
> Hi,
>
> This is a first proposal to discuss the addition of in-fences support
> to DRM. It adds a new struct to fence.c to abstract the use of sync_file
> in DRM drivers. The new struct fence_collection contains a
50 matches
Mail list logo