Lines Matching refs:bit
41 …acing documentation: according to the user-facing documentation, arbitrary 32-bit values are valid.
51 All integers are encoded in little-endian order in 8-bit bytes.
72 Assumption: ITS provides a 32-bit file identifier namespace. The Crypto service can use arbitrary f…
116 …name is just the key identifier as defined in the PSA crypto specification. This is a 32-bit value.
117 …lling partition identifier provided to the server by the partition manager. This is a 64-bit value.
133 Assumption: ITS provides a 64-bit file identifier namespace. The Crypto service can use arbitrary f…
143 Assumption: ITS provides a 64-bit file identifier namespace. The entity using the crypto library ca…
166 It would simplify things to always have a 32-bit owner, with a nonzero value, and thus reserve the …
188 …_its", key_id)`: a key or non-key file. The `key_id` in the name is the 64-bit file identifier, wh…
201 All integers are encoded in little-endian order in 8-bit bytes.
230 Assumption: ITS provides a 64-bit file identifier namespace. The Crypto service can use arbitrary f…
240 Assumption: ITS provides a 64-bit file identifier namespace. The entity using the crypto library ca…
260 All integers are encoded in little-endian order in 8-bit bytes except where otherwise indicated.
319 All integers are encoded in little-endian order in 8-bit bytes except where otherwise indicated.
369 Assumption: ITS provides a 64-bit file identifier namespace. The Crypto service can use arbitrary f…
379 Assumption: ITS provides a 64-bit file identifier namespace. The entity using the crypto library ca…
395 …_its", key_id)`: a key or non-key file. The `key_id` in the name is the 64-bit file identifier, wh…
405 …he key identifier as defined in the PSA crypto specification. This is a 32-bit value which must be…
406 …lling partition identifier provided to the server by the partition manager. This is a 64-bit value.
410 All integers are encoded in little-endian order in 8-bit bytes except where otherwise indicated.