Am 25.04.2013 18:40, schrieb Alex Deucher:
> On Thu, Apr 25, 2013 at 12:19 PM, Christian K?nig
> <deathsimple at vodafone.de> wrote:
>> From: Christian K?nig <christian.koenig at amd.com>
>>
>> This avoid moving the BO directly after allocating it.
>>
>> Signed-off-by: Christian K?nig <christian.koenig at amd.com>
> Looks good. Applied to my tree.
Have you also seen/applied "[PATCH] drm/radeon: fix scratch reg handling
for UVD fence"?
That one is more important cause it fixes a real bug, while this patch
is just a cleanup.
Christian.
> Alex
>
>> ---
>> drivers/gpu/drm/radeon/radeon_sa.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/radeon/radeon_sa.c
>> b/drivers/gpu/drm/radeon/radeon_sa.c
>> index cb80099..0abe5a9 100644
>> --- a/drivers/gpu/drm/radeon/radeon_sa.c
>> +++ b/drivers/gpu/drm/radeon/radeon_sa.c
>> @@ -64,7 +64,7 @@ int radeon_sa_bo_manager_init(struct radeon_device *rdev,
>> }
>>
>> r = radeon_bo_create(rdev, size, RADEON_GPU_PAGE_SIZE, true,
>> - RADEON_GEM_DOMAIN_CPU, NULL, &sa_manager->bo);
>> + domain, NULL, &sa_manager->bo);
>> if (r) {
>> dev_err(rdev->dev, "(%d) failed to allocate bo for
>> manager\n", r);
>> return r;
>> --
>> 1.7.10.4
>>
