From: Felix Kuehling <felix.kuehling@amd.com>
To: Peter Maucher <bellosilicio@gmail.com>,
alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] drm/amdgpu: add GART and GTT to glossary
Date: Thu, 1 Dec 2022 16:51:03 -0500 [thread overview]
Message-ID: <36f2e82a-4f60-bc85-3146-e04ce68923a8@amd.com> (raw)
In-Reply-To: <20221201153820.257570-3-bellosilicio@gmail.com>
On 2022-12-01 10:38, Peter Maucher wrote:
> GART and GTT are two abbreviations that should be mentioned in the
> glossary.
>
> Signed-off-by: Peter Maucher <bellosilicio@gmail.com>
> ---
> Documentation/gpu/amdgpu/amdgpu-glossary.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/gpu/amdgpu/amdgpu-glossary.rst b/Documentation/gpu/amdgpu/amdgpu-glossary.rst
> index 326896e9800d..d86bea7926dc 100644
> --- a/Documentation/gpu/amdgpu/amdgpu-glossary.rst
> +++ b/Documentation/gpu/amdgpu/amdgpu-glossary.rst
> @@ -30,6 +30,12 @@ we have a dedicated glossary for Display Core at
> EOP
> End Of Pipe/Pipeline
>
> + GART
> + Graphics Aperture Table
The "R" stands for "Remapping". I've usually seen this as "Graphics
Address Remapping Table", but "... Aperture ..." would work too.
Regards,
Felix
> +
> + GTT
> + Graphics Translation Table, mostly synonymous to GART
> +
> GC
> Graphics and Compute
>
next prev parent reply other threads:[~2022-12-01 21:51 UTC|newest]
Thread overview: 6+ 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 [this message]
2022-12-01 15:38 ` [PATCH 3/3] drm/amdgpu: mention RDNA support in docu Peter Maucher
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=36f2e82a-4f60-bc85-3146-e04ce68923a8@amd.com \
--to=felix.kuehling@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bellosilicio@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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