| /u-boot/include/ |
| A D | kgdb.h | 37 unsigned long private[KGDBDATA_MAXPRIV]; member
|
| /u-boot/doc/uImage.FIT/ |
| A D | verified-boot.txt | 25 Images are signed using a private key known only to the signer, but can 27 made available without risk to the verification process. The private and 76 1. Master private key is used by the signer to sign a first-stage image. 78 2. Secondary private key is created and used to sign second-stage images.
|
| A D | signature.txt | 10 The signature feature allows the hash to be signed with a private key such 11 that it can be verified using a public key later. Provided that the private 25 - sign the hash with a private key to produce a signature 67 To create a new public/private key pair, size 2048 bits: 92 private key is stored in <name>.key and the certificate is stored in 473 Securely managing private signing keys can challenging, especially when the 503 "pkcs11:<keydir>;object=<key-name-hint>;type=<public|private>" 505 "pkcs11:<keydir>;type=<public|private>" 507 "pkcs11:object=<key-name-hint>;type=<public|private>", 618 Use the URL of the token to list the private keys: [all …]
|
| /u-boot/arch/powerpc/lib/ |
| A D | kgdb.c | 85 kdp->private[0] = msr = get_msr(); in kgdb_enter() 109 unsigned long msr = kdp->private[0]; in kgdb_exit()
|
| /u-boot/doc/ |
| A D | README.udp | 22 The pointer data is used to store private data that
|
| A D | README.t1040-l2switch | 47 ethsw vlan fdb { [help] | show | shared | private } - make VLAN learning shared or private
|
| A D | README.armada-secureboot | 176 secured boot image: The KAK private key and a CSK private key (both have to be 180 NOTE: Since the public key can be generated from the private key, it is 181 sufficient to store the private key for each key pair. 192 Alternatively, instead of copying the files, symlinks to the private keys can 195 WARNING: Knowledge of the KAK or CSK private key would enable an attacker to 196 generate secured boot images containing arbitrary code. Hence, the private keys 210 KAK - The name of the KAK RSA private key file in the U-Boot 212 CSK - The name of the (active) CSK RSA private key file in the
|
| /u-boot/arch/arm/dts/ |
| A D | omap5-l4-abe.dtsi | 107 reg = <0x0 0xff>, /* MPU private access */ 140 reg = <0x0 0xff>, /* MPU private access */ 173 reg = <0x0 0xff>, /* MPU private access */ 225 reg = <0x0 0x7f>, /* MPU private access */ 268 reg = <0x0 0x7f>, /* MPU private access */
|
| A D | omap4-l4-abe.dtsi | 107 reg = <0x0 0xff>, /* MPU private access */ 140 reg = <0x0 0xff>, /* MPU private access */ 173 reg = <0x0 0xff>, /* MPU private access */ 241 reg = <0x0 0x7f>, /* MPU private access */ 303 reg = <0x0 0x7f>, /* MPU private access */
|
| /u-boot/fs/btrfs/ |
| A D | extent-io.c | 522 int set_state_private(struct extent_io_tree *tree, u64 start, u64 private) in set_state_private() argument 538 state->xprivate = private; in set_state_private() 543 int get_state_private(struct extent_io_tree *tree, u64 start, u64 *private) in get_state_private() argument 559 *private = state->xprivate; in get_state_private()
|
| /u-boot/doc/imx/habv4/ |
| A D | introduction_habv4.txt | 30 algorithm in which image data is signed offline using a series of private 136 software to have its own private blobs that cannot be decapsulated or 146 The first step is to generate the private keys and public keys certificates. 187 After running the script users can check the private keys under keys/ directory
|
| /u-boot/drivers/adc/ |
| A D | Kconfig | 58 Each has its own private registers, but shares some resources:
|
| /u-boot/doc/driver-model/ |
| A D | serial-howto.rst | 24 - Add a private struct for the driver data - avoid using static variables
|
| A D | i2c-howto.rst | 34 - Add a private struct for the driver data - avoid using static variables
|
| A D | spi-howto.rst | 13 Before driver model, SPI drivers have their own private structure which 17 driver-specific slave structure can now be port in private data for the 30 SPI's buses private data. 293 Add the device private data 296 Most devices have some private data which they use to keep track of things
|
| A D | usb-info.rst | 61 The driver can use priv_auto to set the size of its private data. 109 This is private information for each controller, maintained by the 229 speed) in its parent platform data. We cannot store it its private data 236 stored in the parent platform data and stores it in the parent private data 285 - they both attach private data to their children (struct usb_device,
|
| /u-boot/arch/x86/dts/ |
| A D | u-boot.dtsi | 141 private_files: private-files {
|
| /u-boot/doc/imx/clk/ |
| A D | ccf.txt | 51 (via private_alloc_size) device private data (accessible via dev->priv). It 52 may look appealing to use this feature to allocate private structures for CCF
|
| /u-boot/drivers/bios_emulator/include/x86emu/ |
| A D | regs.h | 310 void *private; member
|
| /u-boot/doc/build/ |
| A D | clang.rst | 15 Also AArch64 is not supported currently due to a lack of private libgcc
|
| /u-boot/doc/board/emulation/ |
| A D | qemu-mips.rst | 231 Discard symbol table from `/private/u-boot-arm/u-boot'? (y or n) y 239 Reading symbols from /private/u-boot-arm/u-boot...done.
|
| A D | qemu_capsule_update.rst | 101 The public and private keys used for the signing process are generated 127 --update-image-index <val> --signer-private-cert \
|
| /u-boot/doc/board/amlogic/ |
| A D | beelink-gtking.rst | 39 detected. The following FIPs were generated with newer private sources
|
| A D | beelink-gtkingpro.rst | 40 detected. The following FIPs were generated with newer private sources
|
| /u-boot/arch/arm/cpu/armv7/ |
| A D | nonsec_virt.S | 171 str r1, [r3, #GICD_IGROUPRn] @ allow private interrupts
|