dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Alex Deucher <alexdeucher@gmail.com>, dri-devel@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>, stable@vger.kernel.org
Subject: Re: [PATCH 1/8] drm/amdgpu: move gmc7 support out of CIK dependency
Date: Wed, 3 Feb 2016 13:28:21 +0100	[thread overview]
Message-ID: <56B1F265.5020800@vodafone.de> (raw)
In-Reply-To: <56B12501.1050602@vodafone.de>

Am 02.02.2016 um 22:52 schrieb Christian König:
> Am 02.02.2016 um 22:36 schrieb Alex Deucher:
>> It's used by iceland which is VI.
>>
>> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>> Cc: stable@vger.kernel.org
>
> Nice work, the full set is Reviewed-by: Christian König 
> <christian.koenig@amd.com>
>
> Going to test it tomorrow as well.

I wasn't motivated enough to install the full userspace stack as well, 
but a quick test of the kernel module seems to indicate that everything 
works fine now.

Patches are Tested-by: Christian König <christian.koenig@amd.com> as well.

Regards,
Christian.

>
> Christian.
>
>> ---
>>   drivers/gpu/drm/amd/amdgpu/Makefile | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/Makefile 
>> b/drivers/gpu/drm/amd/amdgpu/Makefile
>> index 66f729e..20c9539 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/Makefile
>> +++ b/drivers/gpu/drm/amd/amdgpu/Makefile
>> @@ -25,7 +25,7 @@ amdgpu-y += amdgpu_device.o amdgpu_kms.o \
>>       amdgpu_ucode.o amdgpu_bo_list.o amdgpu_ctx.o amdgpu_sync.o
>>     # add asic specific block
>> -amdgpu-$(CONFIG_DRM_AMDGPU_CIK)+= cik.o gmc_v7_0.o cik_ih.o kv_smc.o 
>> kv_dpm.o \
>> +amdgpu-$(CONFIG_DRM_AMDGPU_CIK)+= cik.o cik_ih.o kv_smc.o kv_dpm.o \
>>       ci_smc.o ci_dpm.o dce_v8_0.o gfx_v7_0.o cik_sdma.o uvd_v4_2.o 
>> vce_v2_0.o \
>>       amdgpu_amdkfd_gfx_v7.o
>>   @@ -34,6 +34,7 @@ amdgpu-y += \
>>     # add GMC block
>>   amdgpu-y += \
>> +    gmc_v7_0.o \
>>       gmc_v8_0.o
>>     # add IH block
>

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2016-02-03 12:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 21:36 [PATCH 1/8] drm/amdgpu: move gmc7 support out of CIK dependency Alex Deucher
2016-02-02 21:36 ` [PATCH 2/8] drm/amdgpu: iceland use CI based MC IP Alex Deucher
2016-02-02 21:36 ` [PATCH 3/8] drm/amdgpu: The VI specific EXE bit should only apply to GMC v8.0 above Alex Deucher
2016-02-02 21:36 ` [PATCH 4/8] drm/amdgpu: pull topaz gmc bits into gmc_v7 Alex Deucher
2016-02-02 21:36 ` [PATCH 5/8] drm/amdgpu: drop topaz support from gmc8 module Alex Deucher
2016-02-02 21:36 ` [PATCH 6/8] drm/amdgpu: don't load MEC2 on topaz Alex Deucher
2016-02-02 21:36 ` [PATCH 7/8] drm/amdgpu: load MEC ucode manually on iceland Alex Deucher
2016-02-02 21:36 ` [PATCH 8/8] drm/amdgpu: remove exp hardware support from iceland Alex Deucher
2016-02-02 21:52 ` [PATCH 1/8] drm/amdgpu: move gmc7 support out of CIK dependency Christian König
2016-02-03 12:28   ` Christian König [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56B1F265.5020800@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox