From: Rhys Kidd <rhyskidd@gmail.com>
To: Ben Skeggs <bskeggs@redhat.com>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Karol Herbst <kherbst@redhat.com>,
Lyude Paul <lyude@redhat.com>, Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Rhys Kidd <rhyskidd@gmail.com>
Subject: [PATCH 0/2] drm/nouveau/bios/init: Improve pre-PMU devinit opcode coverage
Date: Mon, 3 Jun 2019 00:13:13 +1000 [thread overview]
Message-ID: <20190602141315.6197-1-rhyskidd@gmail.com> (raw)
NVIDIA GPUs include a common scripting language (devinit) that can be
interpreted by a number of "engines", e.g. within a kernel-mode software
driver, the VGA BIOS or an on-board small microcontroller which provides
certain security assertions (the 'PMU').
This system allows a GPU programming sequence to be shared by multiple
entities that would not otherwise be able to execute common code.
This series adds support to nouveau for two opcodes seen on VBIOSes prior
to the locked-down PMU taking over responsibility for executing devinit
scripts.
Documentation for these two opcodes can be found at:
https://github.com/envytools/envytools/pull/189
Rhys Kidd (2):
drm/nouveau/bios/init: handle INIT_RESET_BEGUN devinit opcode
drm/nouveau/bios/init: handle INIT_RESET_END devinit opcode
.../gpu/drm/nouveau/nvkm/subdev/bios/init.c | 26 +++++++++++++++++--
1 file changed, 24 insertions(+), 2 deletions(-)
--
2.20.1
next reply other threads:[~2019-06-02 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 14:13 Rhys Kidd [this message]
2019-06-02 14:13 ` [PATCH 1/2] drm/nouveau/bios/init: handle INIT_RESET_BEGUN devinit opcode Rhys Kidd
2019-06-02 14:13 ` [PATCH 2/2] drm/nouveau/bios/init: handle INIT_RESET_END " Rhys Kidd
2019-06-04 18:07 ` [PATCH 0/2] drm/nouveau/bios/init: Improve pre-PMU devinit opcode coverage Lyude Paul
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=20190602141315.6197-1-rhyskidd@gmail.com \
--to=rhyskidd@gmail.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@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