On 16/02/22 1:37 pm, Arunpravin wrote:
>
>
> On 14/02/22 2:42 pm, Christian König wrote:
>>
>>
>> Am 14.02.22 um 09:36 schrieb Matthew Auld:
>>> On Mon, 14 Feb 2022 at 06:32, Christian König
>>> wrote:
Am 13.02.22 um 09:52 schrieb Arunpravin:
> - Make drm_buddy_alloc a single functio
On 14/02/22 2:42 pm, Christian König wrote:
>
>
> Am 14.02.22 um 09:36 schrieb Matthew Auld:
>> On Mon, 14 Feb 2022 at 06:32, Christian König
>> wrote:
>>> Am 13.02.22 um 09:52 schrieb Arunpravin:
- Make drm_buddy_alloc a single function to handle
range allocation and non-range
Am 14.02.22 um 09:36 schrieb Matthew Auld:
On Mon, 14 Feb 2022 at 06:32, Christian König
wrote:
Am 13.02.22 um 09:52 schrieb Arunpravin:
- Make drm_buddy_alloc a single function to handle
range allocation and non-range allocation demands
- Implemented a new function alloc_range() which
On Mon, 14 Feb 2022 at 06:32, Christian König
wrote:
>
> Am 13.02.22 um 09:52 schrieb Arunpravin:
> > - Make drm_buddy_alloc a single function to handle
> >range allocation and non-range allocation demands
> >
> > - Implemented a new function alloc_range() which allocates
> >the requested
Am 13.02.22 um 09:52 schrieb Arunpravin:
- Make drm_buddy_alloc a single function to handle
range allocation and non-range allocation demands
- Implemented a new function alloc_range() which allocates
the requested power-of-two block comply with range limitations
- Moved order computation
- Make drm_buddy_alloc a single function to handle
range allocation and non-range allocation demands
- Implemented a new function alloc_range() which allocates
the requested power-of-two block comply with range limitations
- Moved order computation and memory alignment logic from
i915 drive
