On Fri, Aug 19, 2016 at 11:45 AM, Michel Dänzer <mic...@daenzer.net> wrote:
> On 19/08/16 06:24 PM, Marek Olšák wrote:
>> I've added this. The dmesg message is gone, but the cursor is still missing.
>>
>> diff --git a/src/amdgpu_kms.c b/src/amdgpu_kms.c
>> index 9ee48df..d9f15a4 100644
>> --- a/src/amdgpu_kms.c
>> +++ b/src/amdgpu_kms.c
>> @@ -929,8 +929,14 @@ Bool AMDGPUPreInit_KMS(ScrnInfoPtr pScrn, int flags)
>> else
>> pAMDGPUEnt->HasCRTC2 = TRUE;
>>
>> - info->cursor_w = CURSOR_WIDTH_CIK;
>> - info->cursor_h = CURSOR_HEIGHT_CIK;
>> + if (info->ChipFamily >= CHIP_FAMILY_TAHITI &&
>> + info->ChipFamily <= CHIP_FAMILY_HAINAN) {
>> + info->cursor_w = CURSOR_WIDTH;
>> + info->cursor_h = CURSOR_HEIGHT;
>> + } else {
>> + info->cursor_w = CURSOR_WIDTH_CIK;
>> + info->cursor_h = CURSOR_HEIGHT_CIK;
>> + }
>>
>> amdgpu_query_heap_size(pAMDGPUEnt->pDev, AMDGPU_GEM_DOMAIN_GTT,
>> &heap_size, &max_allocation);
>
> Looks good; does the HW cursor work with the modesetting driver?
No, the cursor doesn't work with modesetting either. There are no
errors in dmesg.
Marek
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
