Displaying 3 results from an estimated 3 matches for "nvkm_firmwar".
Did you mean:
nvkm_firmware
2016 Jan 18
0
[PATCH 0/5] nouveau: unified firmware loading functions
...ficially provided by
> NVIDIA should be looked up using the new functions for consistency.
>
> These new functions are also used by the secure boot series, which will follow
> shortly.
>
> Alexandre Courbot (5):
> core: add firmware handling functions
> gr/gf100: use the nvkm_firmware functions
> falcon: use the nvkm_firmware functions
> xtensa: use the nvkm_firmware functions
> bios: use the nvkm_firmware functions
>
> drm/nouveau/include/nvkm/core/firmware.h | 11 ++++++
> drm/nouveau/nvkm/core/Kbuild | 1 +
> drm/nouveau/nvkm/core/fir...
2016 Jan 18
8
[PATCH 0/5] nouveau: unified firmware loading functions
...es 3-5. At the very least, firmware officially provided by
NVIDIA should be looked up using the new functions for consistency.
These new functions are also used by the secure boot series, which will follow
shortly.
Alexandre Courbot (5):
core: add firmware handling functions
gr/gf100: use the nvkm_firmware functions
falcon: use the nvkm_firmware functions
xtensa: use the nvkm_firmware functions
bios: use the nvkm_firmware functions
drm/nouveau/include/nvkm/core/firmware.h | 11 ++++++
drm/nouveau/nvkm/core/Kbuild | 1 +
drm/nouveau/nvkm/core/firmware.c | 64 +++++++++++++...
2024 Apr 26
3
[PATCH 1/2] drm/nouveau/firmware: Fix SG_DEBUG error with nvkm_firmware_ctor()
...CR4: 00000000003506f0
Call Trace:
<TASK>
? die+0x36/0x90
? do_trap+0xdd/0x100
? sg_init_one+0x85/0xa0
? do_error_trap+0x65/0x80
? sg_init_one+0x85/0xa0
? exc_invalid_op+0x50/0x70
? sg_init_one+0x85/0xa0
? asm_exc_invalid_op+0x1a/0x20
? sg_init_one+0x85/0xa0
nvkm_firmware_ctor+0x14a/0x250 [nouveau]
nvkm_falcon_fw_ctor+0x42/0x70 [nouveau]
ga102_gsp_booter_ctor+0xb4/0x1a0 [nouveau]
r535_gsp_oneinit+0xb3/0x15f0 [nouveau]
? srso_return_thunk+0x5/0x5f
? srso_return_thunk+0x5/0x5f
? nvkm_udevice_new+0x95/0x140 [nouveau]
? srso_return_thunk+0x5/0x5f...