AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Kuehling <felix.kuehling@amd.com>
To: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/amdgpu: mention RDNA support in docu
Date: Thu, 1 Dec 2022 16:54:56 -0500	[thread overview]
Message-ID: <bd1c195d-eac3-d83e-ba84-7a2e38fcafcb@amd.com> (raw)
In-Reply-To: <20221201153820.257570-4-bellosilicio@gmail.com>

On 2022-12-01 10:38, Peter Maucher wrote:
> The amdgpu kernel module has supported RDNA for a while,
> mention that in the module description.
>
> Signed-off-by: Peter Maucher <bellosilicio@gmail.com>
> ---
>   Documentation/gpu/amdgpu/index.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/gpu/amdgpu/index.rst b/Documentation/gpu/amdgpu/index.rst
> index a24e1cfa7407..bcc0f5c15f93 100644
> --- a/Documentation/gpu/amdgpu/index.rst
> +++ b/Documentation/gpu/amdgpu/index.rst
> @@ -3,7 +3,7 @@
>   ==========================
>   
>   The drm/amdgpu driver supports all AMD Radeon GPUs based on the Graphics Core
> -Next (GCN) architecture.
> +Next (GCN) and Radeon DNA (RDNA) architectures.

RDNA is still based on the GCN architecture. If you call out RDNA 
specifically, you'll also have to mention CDNA for completeness. But 
once you go down that route, you'll have to update this again when a new 
marketing name is invented. I'm not sure it's worth it.

Regards,
   Felix


>   
>   .. toctree::
>   

  reply	other threads:[~2022-12-01 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 15:38 [PATCH 0/3] amdgpu/drm: Documentation updates Peter Maucher
2022-12-01 15:38 ` [PATCH 1/3] drm/amdgpu: improve GART and GTT documentation Peter Maucher
2022-12-01 15:38 ` [PATCH 2/3] drm/amdgpu: add GART and GTT to glossary Peter Maucher
2022-12-01 21:51   ` Felix Kuehling
2022-12-01 15:38 ` [PATCH 3/3] drm/amdgpu: mention RDNA support in docu Peter Maucher
2022-12-01 21:54   ` Felix Kuehling [this message]
2022-12-01 16:23 ` [PATCH 0/3] amdgpu/drm: Documentation updates Alex Deucher

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=bd1c195d-eac3-d83e-ba84-7a2e38fcafcb@amd.com \
    --to=felix.kuehling@amd.com \
    --cc=amd-gfx@lists.freedesktop.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