Displaying 2 results from an estimated 2 matches for "acr_v1_gm20b".
2016 Oct 11
0
[PATCH 0/8] Secure Boot refactoring
...e big refactoring occurs. It looks scary, but is really
> just
> moving code (and introducing the nvkm_acr structures).
>
> Patch 6, 7 and 8 remove a few HS hooks that turn out to be unneeded, and
> add
> support for LS hooks.
>
> The end result can be observed by looking at acr_v1_gm20b.c: all the
> specifics
> of GM20B's firmware are handled in a single file, with no data structures
> shared
> with acr_v1.c. The gm20b_acr_v1_ls_func variable also describes clearly
> what
> LS firmwares are to be loaded and how.
>
> Alexandre Courbot (8):
> core: c...
2016 Oct 11
10
[PATCH 0/8] Secure Boot refactoring
...g its actual use.
Patch 5 is where the big refactoring occurs. It looks scary, but is really just
moving code (and introducing the nvkm_acr structures).
Patch 6, 7 and 8 remove a few HS hooks that turn out to be unneeded, and add
support for LS hooks.
The end result can be observed by looking at acr_v1_gm20b.c: all the specifics
of GM20B's firmware are handled in a single file, with no data structures shared
with acr_v1.c. The gm20b_acr_v1_ls_func variable also describes clearly what
LS firmwares are to be loaded and how.
Alexandre Courbot (8):
core: constify nv*_printk macros
core: add falcon...