Lines Matching refs:algorithm
3980 authenticated decryption algorithm to be used to decrypt firmware/s during
4355 \sphinxcode{\sphinxupquote{KEY\_ALG}}: This build flag enables the user to select the algorithm to …
4358 \sphinxcode{\sphinxupquote{rsa\_1\_5}} is the legacy PKCS\#1 RSA 1.5 algorithm which is not TBBR
4365 the algorithm specified by \sphinxcode{\sphinxupquote{KEY\_ALG}}. The valid values for \sphinxcode{…
4366 depend on the chosen algorithm and the cryptographic module.
4409 algorithm. It accepts 3 values: \sphinxcode{\sphinxupquote{sha256}}, \sphinxcode{\sphinxupquote{sha…
6325 \PYG{n}{algorithm} \PYG{n}{OBJECT} \PYG{n}{IDENTIFIER}\PYG{p}{,}
6326 …\PYG{n}{parameters} \PYG{n}{ANY} \PYG{n}{DEFINED} \PYG{n}{BY} \PYG{n}{algorithm} \PYG{n}{OP…
6330 \PYG{n}{algorithm} \PYG{n}{AlgorithmIdentifier}\PYG{p}{,}
23104 …ts/xlat-tables-lib-v2-design:the-memory-mapping-algorithm}]{\sphinxcrossref{The memory mapping alg…
23446 \subsubsection{The memory mapping algorithm}
23447 \label{\detokenize{components/xlat-tables-lib-v2-design:the-memory-mapping-algorithm}}
23449 The mapping function is implemented as a recursive algorithm. It is however
23459 \end{footnote}, the algorithm will attempt to minimize the
23492 about the sorting algorithm in use.
23495 This mapping algorithm does not apply to the MPU library, since the MPU hardware
24525 whatever way is best for a given platform, either through some algorithm or hard
25372 type of hash algorithm used as this information accompanies the hash. This
25374 algorithm implementations.
25416 …\PYG{n}{algorithm} \PYG{n}{AlgorithmIdentifier}\PYG{p}{\PYGZob{}}\PYG{n}{PUBLIC}\PYG{o}{\P…
25426 …\PYG{n}{algorithm} \PYG{n}{ALGORITHM}\PYG{o}{.}\PYG{o}{\PYGZam{}}\PYG{n+nb}{id}\PYG{p}{(}\…
25427 …\PYGZob{}}\PYG{n}{IOSet}\PYG{p}{\PYGZcb{}}\PYG{p}{\PYGZob{}}\PYG{n+nd}{@algorithm}\PYG{p}{\PYGZcb{…
25613 …AM\PYGZus{}SIG\PYGZus{}ALG}\PYG{p}{,}\PYG{+w}{ }\PYG{c+cm}{/* The image signature algorithm */}
25614 …{}PARAM\PYGZus{}HASH}\PYG{p}{,}\PYG{+w}{ }\PYG{c+cm}{/* A hash (including the algorithm) */}
25659 …s{}t}\PYG{+w}{ }\PYG{o}{*}\PYG{n}{alg}\PYG{p}{;}\PYG{+w}{ }\PYG{c+cm}{/* Signature algorithm */}
25926 \sphinxcode{\sphinxupquote{alg}}: the signature algorithm used (obtained from current image)
26099 key, the algorithm, the signature and the data that has been signed. Therefore,
26119 extract the signature algorithm from the certificate.
26223 The mbedTLS library algorithm support is configured by both the
26241 on AES\sphinxhyphen{}GCM algorithm. Valid values are 0 and 1.
27983 therefore BL31 uses locks based on Lamport’s Bakery algorithm instead.
30002 It is a characteristic of Lamport’s Bakery algorithm that the volatile per\sphinxhyphen{}CPU
30026 algorithm mentioned earlier. The bakery\_lock structure only allocates the memory
32388 algorithm to parse the power domain descriptor exported by the platform to
35066 …de{\sphinxupquote{plat/arm/board/common/rotpk/*\_sha256.bin}} depending on the specified algorithm.
46566 SHA256 logs here, as this is the algorithm we used on TF\sphinxhyphen{}A for the measurements