search for: oproxy

...| 2 +- drm/nouveau/include/nvif/client.h | 2 +- drm/nouveau/include/nvif/driver.h | 2 +- drm/nouveau/include/nvkm/core/device.h | 5 ++- drm/nouveau/include/nvkm/core/engine.h | 2 +- drm/nouveau/include/nvkm/core/object.h | 13 ++++++-- drm/nouveau/include/nvkm/core/oproxy.h | 2 +- drm/nouveau/include/nvkm/core/subdev.h | 5 +-- drm/nouveau/include/nvkm/subdev/pci.h | 3 +- drm/nouveau/nouveau_drm.c | 10 +++++- drm/nouveau/nouveau_nvif.c | 6 ++-- drm/nouveau/nvif/client.c | 4 +-- drm/nouveau/nvkm/core/client.c...

On Mon, 21 Sep 2020 at 09:53, Hisashi T Fujinaka <htodd at twofifty.com> wrote: > OK, NetBSD-current amd64, NetBSD-9-amd64, and NetBSD-9-i386 all pass all > tests. MacOS, well, I always try it but it has problems. What's the problem on OS X? We test on it regularly (El Capitan and High Sierra) and the only problem I'm aware of is that the native libcrypto on High Sierra is

...t; + /** @hpd: An event that fires when something happens I guess. */ > > struct nvkm_event hpd; > > + > > + /** @vblank: An event that fires and has some relation to the vblank. */ > > struct nvkm_event vblank; > > > > + /** @client: The oproxy (?) client for this display. */ > > struct nvkm_oproxy *client; > > }; > > generally not a big fan of "int a; // a is an int" kind of > documentation. But if it would specify constraints or details on how > it's valid to use those fields, then it make...

...t fires when something happens I guess. */ > > > struct nvkm_event hpd; > > > + > > > + /** @vblank: An event that fires and has some relation to the vblank. */ > > > struct nvkm_event vblank; > > > > > > + /** @client: The oproxy (?) client for this display. */ > > > struct nvkm_oproxy *client; > > > }; > > > > generally not a big fan of "int a; // a is an int" kind of > > documentation. But if it would specify constraints or details on how > > it's valid to u...

...gt; >>>> struct nvkm_event hpd; > >>>> + > >>>> + /** @vblank: An event that fires and has some relation to the vblank. */ > >>>> struct nvkm_event vblank; > >>>> > >>>> + /** @client: The oproxy (?) client for this display. */ > >>>> struct nvkm_oproxy *client; > >>>> }; > >>> > >>> generally not a big fan of "int a; // a is an int" kind of > >>> documentation. But if it would specify constraints or deta...

...omething happens I guess. */ >>>> struct nvkm_event hpd; >>>> + >>>> + /** @vblank: An event that fires and has some relation to the vblank. */ >>>> struct nvkm_event vblank; >>>> >>>> + /** @client: The oproxy (?) client for this display. */ >>>> struct nvkm_oproxy *client; >>>> }; >>> >>> generally not a big fan of "int a; // a is an int" kind of >>> documentation. But if it would specify constraints or details on how >>> i...

...conn: List of connectors for this display. */ struct list_head conn; + /** @hpd: An event that fires when something happens I guess. */ struct nvkm_event hpd; + + /** @vblank: An event that fires and has some relation to the vblank. */ struct nvkm_event vblank; + /** @client: The oproxy (?) client for this display. */ struct nvkm_oproxy *client; }; diff --git a/drivers/gpu/drm/nouveau/nouveau_drm.c b/drivers/gpu/drm/nouveau/nouveau_drm.c index 22d246acc5e5..c03c18eaee45 100644 --- a/drivers/gpu/drm/nouveau/nouveau_drm.c +++ b/drivers/gpu/drm/nouveau/nouveau_drm.c @@ -68,27 +6...

...struct list_head conn; > > + /** @hpd: An event that fires when something happens I guess. */ > struct nvkm_event hpd; > + > + /** @vblank: An event that fires and has some relation to the vblank. */ > struct nvkm_event vblank; > > + /** @client: The oproxy (?) client for this display. */ > struct nvkm_oproxy *client; > }; generally not a big fan of "int a; // a is an int" kind of documentation. But if it would specify constraints or details on how it's valid to use those fields, then it makes totally sense to add stuff....

...dentifier: GPL-2.0 */ include/nvkm/core/memory.h:/* SPDX-License-Identifier: GPL-2.0 */ include/nvkm/core/mm.h:/* SPDX-License-Identifier: GPL-2.0 */ include/nvkm/core/notify.h:/* SPDX-License-Identifier: GPL-2.0 */ include/nvkm/core/object.h:/* SPDX-License-Identifier: GPL-2.0 */ include/nvkm/core/oproxy.h:/* SPDX-License-Identifier: GPL-2.0 */ include/nvkm/core/option.h:/* SPDX-License-Identifier: GPL-2.0 */ include/nvkm/core/os.h:/* SPDX-License-Identifier: GPL-2.0 */ include/nvkm/core/pci.h:/* SPDX-License-Identifier: GPL-2.0 */ include/nvkm/core/ramht.h:/* SPDX-License-Identifier: GPL-2.0 */ in...

...e/nvkm/core/memory.h | 2 +- drivers/gpu/drm/nouveau/include/nvkm/core/mm.h | 2 +- drivers/gpu/drm/nouveau/include/nvkm/core/notify.h | 2 +- drivers/gpu/drm/nouveau/include/nvkm/core/object.h | 2 +- drivers/gpu/drm/nouveau/include/nvkm/core/oproxy.h | 2 +- drivers/gpu/drm/nouveau/include/nvkm/core/option.h | 2 +- drivers/gpu/drm/nouveau/include/nvkm/core/os.h | 2 +- drivers/gpu/drm/nouveau/include/nvkm/core/pci.h | 2 +- drivers/gpu/drm/nouveau/include/nvkm/core/ramht.h...

Hi everyone, Apologies for the big patchset. This is a rework of the secure boot code that moves the building of the blob into its own set of source files (and own hooks), making the code more flexible and (hopefully) easier to understand as well. This rework is needed to support more signed firmware for existing and new chips. Since the firmwares in question are not available yet I cannot send

This is a rework of the secure boot code that moves the building of the blob into its own set of source files (and own hooks), making the code more flexible and (hopefully) easier to understand as well. This rework is needed to support more signed firmware for existing and new chips. Since the firmwares in question are not available yet I cannot send the code to manage then, but hopefully the

This is a rework of the secure boot code that moves the building of the blob into its own set of source files (and own hooks), making the code more flexible and (hopefully) easier to understand as well. This rework is needed to support more signed firmware for existing and new chips. Since the firmwares in question are not available yet I cannot send the code to manage then, but hopefully the

This revision includes initial signed PMU firmware support for GM20B (Tegra X1). This PMU code will also be used as a basis for dGPU signed PMU firmware support. With the PMU code, the refactoring of secure boot should also make more sense. ACR (secure boot) support is now separated by the driver version it originates from. This separation allows to run any version of the ACR on any chip,