.org
> Subject: Re: [PATCH v2 3/4] drm/exynos: added userptr feature.
>
> On Sat, May 5, 2012 at 6:22 AM, Dave Airlie wrote:
> > On Sat, May 5, 2012 at 11:19 AM, wrote:
> >> Hi Dave,
> >>
> >> 2012. 4. 25. ?? 7:15 Dave Airlie ??:
> >>
> >>
ct: Re: [PATCH v2 3/4] drm/exynos: added userptr feature.
>
> On Sat, May 5, 2012 at 11:19 AM, wrote:
> > Hi Dave,
> >
> > 2012. 4. 25. ?? 7:15 Dave Airlie ??:
> >
> >> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
> >>> this feature could be
ark at samsung.com;
>> sw0312.kim at samsung.com; dri-devel at lists.freedesktop.org
>> Subject: Re: [PATCH v2 3/4] drm/exynos: added userptr feature.
>>
>> On Sat, May 5, 2012 at 6:22 AM, Dave Airlie wrote:
>> > On Sat, May 5, 2012 at 11:19 AM, wrote:
>> >&g
.com;
>> sw0312@samsung.com; dri-devel@lists.freedesktop.org
>> Subject: Re: [PATCH v2 3/4] drm/exynos: added userptr feature.
>>
>> On Sat, May 5, 2012 at 6:22 AM, Dave Airlie wrote:
>> > On Sat, May 5, 2012 at 11:19 AM, wrote:
>> >> Hi Dave,
>&
ct: Re: [PATCH v2 3/4] drm/exynos: added userptr feature.
>
> On Sat, May 5, 2012 at 6:22 AM, Dave Airlie wrote:
> > On Sat, May 5, 2012 at 11:19 AM, wrote:
> >> Hi Dave,
> >>
> >> 2012. 4. 25. 오후 7:15 Dave Airlie 작성:
> >>
> >>> On Tue, A
Hi Dave,
> -Original Message-
> From: Dave Airlie [mailto:airl...@gmail.com]
> Sent: Saturday, May 05, 2012 7:23 PM
> To: daei...@gmail.com
> Cc: Inki Dae; kyungmin.p...@samsung.com; sw0312@samsung.com; dri-
> de...@lists.freedesktop.org
> Subject: Re: [PATCH v2 3
On Sat, May 5, 2012 at 6:22 AM, Dave Airlie wrote:
> On Sat, May 5, 2012 at 11:19 AM, wrote:
>> Hi Dave,
>>
>> 2012. 4. 25. ?? 7:15 Dave Airlie ??:
>>
>>> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
this feature could be used to use memory region allocated by malloc() in
user
>
On Sat, May 5, 2012 at 6:22 AM, Dave Airlie wrote:
> On Sat, May 5, 2012 at 11:19 AM, wrote:
>> Hi Dave,
>>
>> 2012. 4. 25. 오후 7:15 Dave Airlie 작성:
>>
>>> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
this feature could be used to use memory region allocated by malloc() in
user
>
Hi Dave,
2012. 4. 25. ?? 7:15 Dave Airlie ??:
> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
>> this feature could be used to use memory region allocated by malloc() in user
>> mode and mmaped memory region allocated by other memory allocators. userptr
>> interface can identify memory type
On Sat, May 5, 2012 at 11:19 AM, wrote:
> Hi Dave,
>
> 2012. 4. 25. ?? 7:15 Dave Airlie ??:
>
>> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
>>> this feature could be used to use memory region allocated by malloc() in
>>> user
>>> mode and mmaped memory region allocated by other memory al
On Sat, May 5, 2012 at 11:19 AM, wrote:
> Hi Dave,
>
> 2012. 4. 25. 오후 7:15 Dave Airlie 작성:
>
>> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
>>> this feature could be used to use memory region allocated by malloc() in
>>> user
>>> mode and mmaped memory region allocated by other memory al
Hi Dave,
2012. 4. 25. 오후 7:15 Dave Airlie 작성:
> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
>> this feature could be used to use memory region allocated by malloc() in user
>> mode and mmaped memory region allocated by other memory allocators. userptr
>> interface can identify memory type
Hi Dave,
2012/4/25, Dave Airlie :
> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
>> this feature could be used to use memory region allocated by malloc() in
>> user
>> mode and mmaped memory region allocated by other memory allocators.
>> userptr
>> interface can identify memory type through
On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
> this feature could be used to use memory region allocated by malloc() in user
> mode and mmaped memory region allocated by other memory allocators. userptr
> interface can identify memory type through vm_flags value and would get
> pages or page f
Hi Dave,
2012/4/25, Dave Airlie :
> On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
>> this feature could be used to use memory region allocated by malloc() in
>> user
>> mode and mmaped memory region allocated by other memory allocators.
>> userptr
>> interface can identify memory type through
On Tue, Apr 24, 2012 at 6:17 AM, Inki Dae wrote:
> this feature could be used to use memory region allocated by malloc() in user
> mode and mmaped memory region allocated by other memory allocators. userptr
> interface can identify memory type through vm_flags value and would get
> pages or page f
this feature could be used to use memory region allocated by malloc() in user
mode and mmaped memory region allocated by other memory allocators. userptr
interface can identify memory type through vm_flags value and would get
pages or page frame numbers to user space appropriately.
changelog v2:
t
this feature could be used to use memory region allocated by malloc() in user
mode and mmaped memory region allocated by other memory allocators. userptr
interface can identify memory type through vm_flags value and would get
pages or page frame numbers to user space appropriately.
changelog v2:
t
18 matches
Mail list logo
