<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/drivers/gpu/drm/nouveau/nvkm/subdev/secboot/Kbuild, branch linux-4.17.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.17.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.17.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2018-02-02T05:24:05Z</updated>
<entry>
<title>drm/nouveau/secboot/gp108: implement on top of acr_r370</title>
<updated>2018-02-02T05:24:05Z</updated>
<author>
<name>Ben Skeggs</name>
<email>bskeggs@redhat.com</email>
</author>
<published>2017-12-12T06:09:03Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=2c5ac5ba4f855b8cb3f20c52c1a1e0773e671164'/>
<id>urn:sha1:2c5ac5ba4f855b8cb3f20c52c1a1e0773e671164</id>
<content type='text'>
Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
Reviewed-by: Gourav Samaiya &lt;gsamaiya@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/nouveau/secboot/r370: move a bunch of r375 stuff to a new implementation</title>
<updated>2018-02-02T05:24:04Z</updated>
<author>
<name>Ben Skeggs</name>
<email>bskeggs@redhat.com</email>
</author>
<published>2017-12-12T05:50:10Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=b7997a35f936e92de0f69231c3ba6aa7cc6c20f1'/>
<id>urn:sha1:b7997a35f936e92de0f69231c3ba6aa7cc6c20f1</id>
<content type='text'>
It's entirely possibly that the other r375 code is relevant to r370 too,
but I've not confirmed this, so I'll leave it where it is for now.

NVIDIA's copyright headers maintained, as it's still all their code.

Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
Reviewed-by: Gourav Samaiya &lt;gsamaiya@nvidia.com&gt;
</content>
</entry>
<entry>
<title>drm/nouveau/secboot: add GP10B support</title>
<updated>2017-04-06T04:39:04Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2017-03-29T09:31:14Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=59d5592d3bf2e70b9c56212cf5c9f1bfab6f0147'/>
<id>urn:sha1:59d5592d3bf2e70b9c56212cf5c9f1bfab6f0147</id>
<content type='text'>
GP10B's secboot is largely similar to GM20B's. Only differences are MC
base address and the fact that GPCCS is also securely managed.

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/nouveau/secboot: add gp102/gp104/gp106/gp107 support</title>
<updated>2017-03-07T07:05:16Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2017-01-26T06:18:25Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=5429f82f341524deb9f66193892a69dea2f862a3'/>
<id>urn:sha1:5429f82f341524deb9f66193892a69dea2f862a3</id>
<content type='text'>
These gp10x chips are supporting using (roughly) the same firmware.
Compared to previous secure chips, ACR runs on SEC2 and so does the
low-secure msgqueue.

ACR for these chips is based on r367.

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/nouveau/secboot: put HS code loading code into own file</title>
<updated>2017-03-07T07:05:16Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2017-02-16T09:57:03Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=84074e5b10acc7154d5aff8630f9379870e71be6'/>
<id>urn:sha1:84074e5b10acc7154d5aff8630f9379870e71be6</id>
<content type='text'>
We will also need to load HS blobs outside of acr_r352 (for instance, to
run the NVDEC VPR scrubber), so make this code reusable.

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/nouveau/secboot: support for r375 ACR</title>
<updated>2017-03-07T07:05:16Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2016-11-15T07:30:52Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=717bad8273530ca94ae3ff27ff80c90b3721d163'/>
<id>urn:sha1:717bad8273530ca94ae3ff27ff80c90b3721d163</id>
<content type='text'>
r375 ACR uses a unified bootloader descriptor for the GR and PMU
firmwares.

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/nouveau/secboot: support for r367 ACR</title>
<updated>2017-03-07T07:05:16Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2016-11-15T07:30:26Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=0f8fb2ab1e093c031ff4ce91570951e82fef6ca1'/>
<id>urn:sha1:0f8fb2ab1e093c031ff4ce91570951e82fef6ca1</id>
<content type='text'>
r367 uses a different hsflcn_desc layout and LS firmware signature
format, requiring a rewrite of some functions.

It also makes use of the shadow region, and uses SEC as the boot falcon.

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/nouveau/secboot: support for r364 ACR</title>
<updated>2017-03-07T07:05:15Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2016-11-15T06:34:29Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=810997ff40783853491babc5d3d82b510704674f'/>
<id>urn:sha1:810997ff40783853491babc5d3d82b510704674f</id>
<content type='text'>
r364 is similar to r361, but uses a different hsflcn_desc structure to
introduce the shadow region address (even though it is not yet used by
this version).

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/nouveau/secboot: support for loading LS PMU firmware</title>
<updated>2017-03-07T07:05:12Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2016-10-27T05:22:28Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=eabe4ea6a418a60b4df666154f2b0d8cd7d5ba29'/>
<id>urn:sha1:eabe4ea6a418a60b4df666154f2b0d8cd7d5ba29</id>
<content type='text'>
Allow secboot to load a LS PMU firmware. LS PMU is one instance of
firmwares based on the message queue mechanism, which is also used for
other firmwares like SEC, so name its source file accordingly.

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm/nouveau/secboot: reorganize into more files</title>
<updated>2017-02-17T05:14:31Z</updated>
<author>
<name>Alexandre Courbot</name>
<email>acourbot@nvidia.com</email>
</author>
<published>2016-12-14T08:02:39Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=72e0642fb4c21632a410c1ff971a63886402b9c9'/>
<id>urn:sha1:72e0642fb4c21632a410c1ff971a63886402b9c9</id>
<content type='text'>
Split the act of building the ACR blob from firmware files from the rest
of the (chip-dependent) secure boot logic. ACR logic is moved into
acr_rxxx.c files, where rxxx corresponds to the compatible release of
the NVIDIA driver. At the moment r352 and r361 are supported since
firmwares have been released for these versions. Some abstractions are
added on top of r352 so r361 can easily be implemented on top of it by
just overriding a few hooks.

This split makes it possible and easy to reuse the same ACR version on
different chips. It also hopefully makes the code much more readable as
the different secure boot logics are separated. As more chips and
firmware versions will be supported, this is a necessity to not get lost
in code that is already quite complex.

This is a big commit, but it essentially moves things around (and split
the nvkm_secboot structure into two, nvkm_secboot and nvkm_acr). Code
semantics should not be affected.

Signed-off-by: Alexandre Courbot &lt;acourbot@nvidia.com&gt;
Signed-off-by: Ben Skeggs &lt;bskeggs@redhat.com&gt;
</content>
</entry>
</feed>
