search for: fuc41ac

...n 304.123 $ stat -c %s mmiotrace.log 134659197 $ file mmiotrace.log mmiotrace.log: ASCII text $ grep -i lost mmiotrace.log ; echo $? 1 $ ./envytools/rnn/demmio -f mmiotrace.log | perl -e 'open($fh409c, ">fuc409c"); open($fh409d, ">fuc409d"); open($fh41ac, ">fuc41ac"); open($fh41ad, ">fuc41ad");%m = ("0x409184" => $fh409c, "0x4091c4" => $fh409d, "0x41a184" => $fh41ac, "0x41a1c4" => $fh41ad);while (<>) { exit if (/0x409840/); next if (!/W (0x4(?:09|1a)1[c8]4) .* <= (?:.*0x)?(.*)/); p...

...nv_info(priv, "using external firmware\n"); > - if (gf100_gr_ctor_fw(priv, "fuc409c", &priv->fuc409c) || > - gf100_gr_ctor_fw(priv, "fuc409d", &priv->fuc409d) || > - gf100_gr_ctor_fw(priv, "fuc41ac", &priv->fuc41ac) || > - gf100_gr_ctor_fw(priv, "fuc41ad", &priv->fuc41ad)) > + if (gf100_gr_ctor_fw(priv, "fuc409c", "fecs_inst", &priv->fuc409c) || > + gf100_gr_ctor_fw(priv, "f...

...fficially. NVIDIA plans to release firmwares as one file per binary to keep things simple. The layout will be nvidia/<gpu>/<firmware>.bin, so for GK20A FECS/GPCCS we have: nvidia/gk20a/fecs_inst.bin (aka fuc409c) nvidia/gk20a/fecs_data.bin (aka fuc409d) nvidia/gk20a/gpccs_inst.bin (aka fuc41ac) nvidia/gk20a/gpccs_data.bin (aka fuc41ad) All firmware files listed in this patchset are clean for release, and I am just waiting for a community ack of the layout to send a patch to linux-firmware. The second patch reworks existing GK20A support to make it closer to what our nvgpu driver does....

.../* 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 (!legacy_fwname) { nvkm_error(subdev, "failed to load %s\n", fwname); return ret; } - fuc->size = fw->size; - fuc-...

...134659197 > > $ file mmiotrace.log > mmiotrace.log: ASCII text > > $ grep -i lost mmiotrace.log ; echo $? > 1 > > $ ./envytools/rnn/demmio -f mmiotrace.log | perl -e 'open($fh409c, ">fuc409c"); open($fh409d, ">fuc409d"); open($fh41ac, ">fuc41ac"); open($fh41ad, ">fuc41ad");%m = ("0x409184" => $fh409c, "0x4091c4" => $fh409d, "0x41a184" => $fh41ac, "0x41a1c4" => $fh41ad);while (<>) { exit if (/0x409840/); next if (!/W (0x4(?:09|1a)1[c8]4) .* <= (?:.*0x)?(.*)/); p...

...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 (!fwname) { + nvkm_error(subdev, "failed to load %s\n", fwname); + return ret; + } + + /* yes, try to load fro...

...ile mmiotrace.log >> mmiotrace.log: ASCII text >> >> $ grep -i lost mmiotrace.log ; echo $? >> 1 >> >> $ ./envytools/rnn/demmio -f mmiotrace.log | perl -e 'open($fh409c, ">fuc409c"); open($fh409d, ">fuc409d"); open($fh41ac, ">fuc41ac"); open($fh41ad, ">fuc41ad");%m = ("0x409184" => $fh409c, "0x4091c4" => $fh409d, "0x41a184" => $fh41ac, "0x41a1c4" => $fh41ad);while (<>) { exit if (/0x409840/); next if (!/W (0x4(?:09|1a)1[c8]4) .* <= (?:.*0x)?(.*)/); p...

...>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>

...> + 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"; > > As I mentioned on IRC, I find this strcmp thing a little jarring. It > should be pretty easy to just pass the legacy fwname into > gf100_gr_ctor_f...

...+ 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

...f --git a/drm/nouveau/nvkm/engine/gr/gf100.c b/drm/nouveau/nvkm/engine/gr/gf100.c index ed45f92..60a1b5c 100644 --- a/drm/nouveau/nvkm/engine/gr/gf100.c +++ b/drm/nouveau/nvkm/engine/gr/gf100.c @@ -1773,11 +1773,8 @@ gf100_gr_ctor_fw_legacy(struct gf100_gr *gr, const char *fwname, fwname = "fuc41ac"; else if (!strcmp(fwname, "gpccs_data")) fwname = "fuc41ad"; - else - fwname = NULL; - - /* nope, let's just return the error we got */ - if (!fwname) { + else { + /* nope, let's just return the error we got */ nvkm_error(subdev, "failed to load %s\n...

...f 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 (!fwname) { > + nvkm_error(subdev, "failed to load %s\n", fwname); Due t...

This was the first step of the secure boot refactoring - as Ben asked for some fixes, I now submit it as its own series to make it easier to review (and also because rebasing secure boot on top of this takes time and I don't want to do it until this is validated!). This series attempts to factorize the duplicate falcon-related code into a single library, using the existing nvkm_falcon

...cs_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"; As I mentioned on IRC, I find this strcmp thing a little jarring. It should be pretty easy to just pass the legacy fwname into gf100_gr_ctor_fw directly - there are only...

...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"; >> >> As I mentioned on IRC, I find this strcmp thing a little jarring. It >> should be pretty easy to just pass the legacy fwname into &...

...fficially. NVIDIA plans to release firmwares as one file per binary to keep things simple. The layout will be nvidia/<gpu>/<firmware>.bin, so for GK20A FECS/GPCCS we have: nvidia/gk20a/fecs_inst.bin (aka fuc409c) nvidia/gk20a/fecs_data.bin (aka fuc409d) nvidia/gk20a/gpccs_inst.bin (aka fuc41ac) nvidia/gk20a/gpccs_data.bin (aka fuc41ad) All firmware files listed in this patchset are clean for release, and I am just waiting for a community ack of the layout to send a patch to linux-firmware. The second patch reworks existing GK20A support to make it closer to what our nvgpu driver does....

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

This was the first step of the secure boot refactoring - as Ben asked for some fixes, I now submit it as its own series to make it easier to review (and also because rebasing secure boot on top of this takes time and I don't want to do it until this is validated!). This series attempts to factorize the duplicate falcon-related code into a single library, using the existing nvkm_falcon

This series fixes two cases where behavior on secure boot errors could be improved: 1) Patch 2 propages secure-boot errors from GR init, making sure initialization fails as it should. Failure to do so results in a black screen during boot, as reported in FD bug 94990. 2) Patches 3-4 make the absence of required secure firmware files a non-fatal error. The previous behavior was to give up

This is a highly changed revision of the first patch series that adds secure boot support to Nouveau. This code still depends on NVIDIA releasing official firmware files, but the files released with SHIELD TV and Pixel C can already be used on a Jetson TX1. As you know we are working hard to release the official firmware files, however in the meantime it doesn't hurt to review the code so it