search for: fecs_data

...+++++++++++++++++++++++++++++++++- nvidia/gm200/acr/bl.bin | Bin 0 -> 832 bytes nvidia/gm200/acr/ucode_load.bin | Bin 0 -> 10144 bytes nvidia/gm200/acr/ucode_unload.bin | Bin 0 -> 1440 bytes nvidia/gm200/gr/fecs_bl.bin | Bin 0 -> 576 bytes nvidia/gm200/gr/fecs_data.bin | Bin 0 -> 1968 bytes nvidia/gm200/gr/fecs_inst.bin | Bin 0 -> 16271 bytes nvidia/gm200/gr/fecs_sig.bin | Bin 0 -> 76 bytes nvidia/gm200/gr/gpccs_bl.bin | Bin 0 -> 576 bytes nvidia/gm200/gr/gpccs_data.bin | Bin 0 -> 2056 bytes nvidia/gm200/gr/g...

...E | 15 +++++++++++++++ nvidia/gp100/acr/bl.bin | Bin 0 -> 832 bytes nvidia/gp100/acr/ucode_load.bin | Bin 0 -> 9632 bytes nvidia/gp100/acr/ucode_unload.bin | Bin 0 -> 1440 bytes nvidia/gp100/gr/fecs_bl.bin | 1 + nvidia/gp100/gr/fecs_data.bin | Bin 0 -> 2028 bytes nvidia/gp100/gr/fecs_inst.bin | Bin 0 -> 20955 bytes nvidia/gp100/gr/fecs_sig.bin | Bin 0 -> 76 bytes nvidia/gp100/gr/gpccs_bl.bin | 1 + nvidia/gp100/gr/gpccs_data.bin | Bin 0 -> 2080 bytes nvidia/gp100/gr/gpccs_inst.bin...

...MODULE_AUTHOR(DRIVER_AUTHOR); MODULE_DESCRIPTION(DRIVER_DESC); MODULE_LICENSE("GPL and additional rights"); +#if defined(CONFIG_NOUVEAU_PLATFORM_DRIVER) && \ + (IS_ENABLED(CONFIG_ARCH_TEGRA_124_SOC) || IS_ENABLED(CONFIG_ARCH_TEGRA_132_SOC)) +MODULE_FIRMWARE("nvidia/gk20a/fecs_data.bin"); +MODULE_FIRMWARE("nvidia/gk20a/fecs_inst.bin"); +MODULE_FIRMWARE("nvidia/gk20a/gpccs_data.bin"); +MODULE_FIRMWARE("nvidia/gk20a/gpccs_inst.bin"); +MODULE_FIRMWARE("nvidia/gk20a/sw_bundle_init.bin"); +MODULE_FIRMWARE("nvidia/gk20a/sw_ctx.bin&q...

...ata = kmemdup(fw->data, fuc->size, GFP_KERNEL); + nvkm_firmware_put(fw); + return (fuc->data != NULL) ? 0 : -ENOMEM; + } + + /* see if this firmware has a legacy path */ + if (!strcmp(fwname, "fecs_inst")) + legacy_fwname = "fuc409c"; + else if (!strcmp(fwname, "fecs_data")) + legacy_fwname = "fuc409d"; + else if (!strcmp(fwname, "gpccs_inst")) + legacy_fwname = "fuc41ac"; + else if (!strcmp(fwname, "gpccs_data")) + legacy_fwname = "fuc41ad"; + + /* nope, let's just return the error we got */ + if (!legac...

...dev *subdev = &gr->base.engine.subdev; + struct nvkm_device *device = subdev->device; + const struct firmware *fw; + char f[32]; + + /* see if this firmware has a legacy path */ + if (!strcmp(fwname, "fecs_inst")) + fwname = "fuc409c"; + else if (!strcmp(fwname, "fecs_data")) + fwname = "fuc409d"; + else if (!strcmp(fwname, "gpccs_inst")) + fwname = "fuc41ac"; + else if (!strcmp(fwname, "gpccs_data")) + fwname = "fuc41ad"; + else + fwname = NULL; + + /* nope, let's just return the error we got */ + if (!f...

...*func, struct nvkm_device *device,      return ret;      if (gr->firmware) { +          nvkm_info(&gr->base.engine.subdev, "using external firmware\n");                if (gf100_gr_ctor_fw(gr, "fecs_inst", &gr->fuc409c) ||             gf100_gr_ctor_fw(gr, "fecs_data", &gr->fuc409d) ||             gf100_gr_ctor_fw(gr, "gpccs_inst", &gr->fuc41ac) || -- 2.7.3 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20160929/90c6cb87/attachment.html...

...ot; messages disappeared. X works and fbconsole on VT1-VT6 works too. CONFIG_EXTRA_FIRMWARE="nvidia/gp104/gr/sw_nonctx.bin nvidia/gp104/gr/sw_ctx.bin nvidia/gp104/gr/sw_bundle_init.bin nvidia/gp104/gr/sw_method_init.bin nvidia/gp104/gr/fecs_bl.bin nvidia/gp104/gr/fecs_inst.bin nvidia/gp104/gr/fecs_data.bin nvidia/gp104/gr/fecs_sig.bin nvidia/gp104/gr/gpccs_bl.bin nvidia/gp104/gr/gpccs_inst.bin nvidia/gp104/gr/gpccs_data.bin nvidia/gp104/gr/gpccs_sig.bin nvidia/gp104/sec2/image.bin nvidia/gp104/sec2/desc.bin nvidia/gp104/sec2/sig.bin nvidia/gp104/acr/ucode_load.bin nvidia/gp104/acr/ucode_unload.bi...

...fuc->data != NULL) ? 0 : -ENOMEM; >> + } >> + >> + /* see if this firmware has a legacy path */ >> + if (!strcmp(fwname, "fecs_inst")) >> + legacy_fwname = "fuc409c"; >> + else if (!strcmp(fwname, "fecs_data")) >> + legacy_fwname = "fuc409d"; >> + else if (!strcmp(fwname, "gpccs_inst")) >> + legacy_fwname = "fuc41ac"; >> + else if (!strcmp(fwname, "gpccs_data")) >> + legacy_f...

...hese three components can come as files to be directly loaded. However for the current GR firmware we took the approach of splitting the bl, code and data sections into their own files, and building the image and descriptor on-the-fly, as you can see from gm200/gr: gm200/gr/fecs_bl.bin gm200/gr/fecs_data.bin gm200/gr/fecs_inst.bin gm200/gr/fecs_sig.bin The bl, data, and inst files are loaded and combined into an image while the corresponding descriptor is built. This is done in the ls_ucode_img_build() function. The main reason for doing this is there is that for a given GPU generation, the _b...

...ctly loaded. However for >> the current GR firmware we took the approach of splitting the bl, code and >> data sections into their own files, and building the image and descriptor >> on-the-fly, as you can see from gm200/gr: >> >> gm200/gr/fecs_bl.bin >> gm200/gr/fecs_data.bin >> gm200/gr/fecs_inst.bin >> gm200/gr/fecs_sig.bin >> >> The bl, data, and inst files are loaded and combined into an image while the >> corresponding descriptor is built. This is done in the ls_ucode_img_build() >> function. >> >> The main reason...

...we took the approach of splitting the bl, code >>>> and >>>> data sections into their own files, and building the image and descriptor >>>> on-the-fly, as you can see from gm200/gr: >>>> >>>> gm200/gr/fecs_bl.bin >>>> gm200/gr/fecs_data.bin >>>> gm200/gr/fecs_inst.bin >>>> gm200/gr/fecs_sig.bin >>>> >>>> The bl, data, and inst files are loaded and combined into an image while >>>> the >>>> corresponding descriptor is built. This is done in the >>>>...

..._(const struct gf100_gr_func *func, struct nvkm_device *device, return ret; if (gr->firmware) { + nvkm_info(&gr->base.engine.subdev, "using external firmware\n"); if (gf100_gr_ctor_fw(gr, "fecs_inst", &gr->fuc409c) || gf100_gr_ctor_fw(gr, "fecs_data", &gr->fuc409d) || gf100_gr_ctor_fw(gr, "gpccs_inst", &gr->fuc41ac) || -- 2.7.3

.../drm/nouveau/nouveau_platform.c @@ -65,3 +65,14 @@ struct platform_driver nouveau_platform_driver = { .probe = nouveau_platform_probe, .remove = nouveau_platform_remove, }; + +#if IS_ENABLED(CONFIG_ARCH_TEGRA_124_SOC) || IS_ENABLED(CONFIG_ARCH_TEGRA_132_SOC) +MODULE_FIRMWARE("nvidia/gk20a/fecs_data.bin"); +MODULE_FIRMWARE("nvidia/gk20a/fecs_inst.bin"); +MODULE_FIRMWARE("nvidia/gk20a/gpccs_data.bin"); +MODULE_FIRMWARE("nvidia/gk20a/gpccs_inst.bin"); +MODULE_FIRMWARE("nvidia/gk20a/sw_bundle_init.bin"); +MODULE_FIRMWARE("nvidia/gk20a/sw_ctx.bin&q...

...bdev; > + struct nvkm_device *device = subdev->device; > + const struct firmware *fw; > + char f[32]; > + > + /* see if this firmware has a legacy path */ > + if (!strcmp(fwname, "fecs_inst")) > + fwname = "fuc409c"; > + else if (!strcmp(fwname, "fecs_data")) > + fwname = "fuc409d"; > + else if (!strcmp(fwname, "gpccs_inst")) > + fwname = "fuc41ac"; > + else if (!strcmp(fwname, "gpccs_data")) > + fwname = "fuc41ad"; > + else > + fwname = NULL; > + > + /* nope, let...

...and >>>>>> data sections into their own files, and building the image and >>>>>> descriptor >>>>>> on-the-fly, as you can see from gm200/gr: >>>>>> >>>>>> gm200/gr/fecs_bl.bin >>>>>> gm200/gr/fecs_data.bin >>>>>> gm200/gr/fecs_inst.bin >>>>>> gm200/gr/fecs_sig.bin >>>>>> >>>>>> The bl, data, and inst files are loaded and combined into an image >>>>>> while >>>>>> the >>>>>&gt...

...+ return (fuc->data != NULL) ? 0 : -ENOMEM; > + } > + > + /* see if this firmware has a legacy path */ > + if (!strcmp(fwname, "fecs_inst")) > + legacy_fwname = "fuc409c"; > + else if (!strcmp(fwname, "fecs_data")) > + legacy_fwname = "fuc409d"; > + else if (!strcmp(fwname, "gpccs_inst")) > + legacy_fwname = "fuc41ac"; > + else if (!strcmp(fwname, "gpccs_data")) > + legacy_fwname = "fuc41a...

...come as files to be directly loaded. However for > the current GR firmware we took the approach of splitting the bl, code and > data sections into their own files, and building the image and descriptor > on-the-fly, as you can see from gm200/gr: > > gm200/gr/fecs_bl.bin > gm200/gr/fecs_data.bin > gm200/gr/fecs_inst.bin > gm200/gr/fecs_sig.bin > > The bl, data, and inst files are loaded and combined into an image while the > corresponding descriptor is built. This is done in the ls_ucode_img_build() > function. > > The main reason for doing this is there is that...

...0 : -ENOMEM; >>> + } >>> + >>> + /* see if this firmware has a legacy path */ >>> + if (!strcmp(fwname, "fecs_inst")) >>> + legacy_fwname = "fuc409c"; >>> + else if (!strcmp(fwname, "fecs_data")) >>> + legacy_fwname = "fuc409d"; >>> + else if (!strcmp(fwname, "gpccs_inst")) >>> + legacy_fwname = "fuc41ac"; >>> + else if (!strcmp(fwname, "gpccs_data")) >>> +...

New version of the secure boot code that works with the blobs just merged into linux-firmware. Since the required Mesa patches are also merged, this set is the last piece of the puzzle to get out-of-the-box accelerated Maxwell 2. The basic code remains the same, with a few improvements with respect to how secure falcons are started. Hopefully the patchset is better split too. I have a

...the current GR firmware we took the approach of splitting the bl, code >>> and >>> data sections into their own files, and building the image and descriptor >>> on-the-fly, as you can see from gm200/gr: >>> >>> gm200/gr/fecs_bl.bin >>> gm200/gr/fecs_data.bin >>> gm200/gr/fecs_inst.bin >>> gm200/gr/fecs_sig.bin >>> >>> The bl, data, and inst files are loaded and combined into an image while >>> the >>> corresponding descriptor is built. This is done in the >>> ls_ucode_img_build() >&g...