Searched full:environment (Results 1 – 25 of 204) sorted by relevance
123456789
| /Documentation/arch/powerpc/ |
| D | isa-versions.rst | 25 - PowerPC Virtual Environment Architecture Book II v2.02
26 - PowerPC Operating Environment Architecture Book III v2.02
28 - PowerPC Virtual Environment Architecture Book II v2.01
29 - PowerPC Operating Environment Architecture Book III v2.01
32 - PowerPC Virtual Environment Architecture Book II v2.01
33 - PowerPC Operating Environment Architecture Book III v2.01
35 - PowerPC Virtual Environment Architecture Book II v2.00
36 - PowerPC Operating Environment Architecture Book III v2.00
|
| /Documentation/kbuild/ |
| D | kconfig.rst | 39 Environment variables
42 Environment variables for ``*config``:
45 This environment variable can be used to specify a default kernel config
49 This environment variable specifies a list of config files which can be
55 If you set KCONFIG_OVERWRITECONFIG in the environment, Kconfig will not
59 This environment variable makes Kconfig warn about all unrecognized
66 If you set ``CONFIG_`` in the environment, Kconfig will prefix all symbols
70 Environment variables for ``{allyes/allmod/allno/rand}config``:
74 use the environment variable KCONFIG_ALLCONFIG as a flag or a filename
108 Environment variables for ``randconfig``:
[all …]
|
| /Documentation/tee/ |
| D | amd-tee.rst | 4 AMD-TEE (AMD's Trusted Execution Environment)
7 The AMD-TEE driver handles the communication with AMD's TEE environment. The
8 TEE environment is provided by AMD Secure Processor.
12 software-based Trusted Execution Environment (TEE) designed to enable
56 TEE environment.
57 * TEE_CMD_ID_UNLOAD_TA - unloads TA binary from TEE environment.
79 talk to AMD's TEE. AMD's TEE provides a secure environment for loading, opening
|
| D | tee.rst | 4 TEE (Trusted Execution Environment)
12 A TEE is a trusted OS running in some secure environment, for example,
|
| /Documentation/filesystems/ |
| D | gfs2-uevents.rst | 22 The ADD uevent has two environment variables: SPECTATOR=[0|1]
31 has the same environment variables as the ADD uevent. The ONLINE
32 uevent, along with the two environment variables for spectator and
46 two environment variables, JID= which specifies the journal id which
54 without checking the environment variables to discover the state, we
78 Information common to all GFS2 uevents (uevent environment variables)
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ppi | 31 executed in the pre-OS environment. It is the only input from
32 the OS to the pre-OS environment. The request should be an
60 operation to be executed in the pre-OS environment by the BIOS
71 operation to be executed in the pre-OS environment by the BIOS
|
| D | sysfs-uevent | 25 ``SYNTH_UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`` environment
29 ``SYNTH_UUID=0`` environment variable automatically.
|
| D | sysfs-bus-iio-proximity | 21 sensor and its operating environment:
|
| /Documentation/devicetree/bindings/firmware/ |
| D | mediatek,geniezone.yaml | 14 providing an isolated execution environment for mTEE (MediaTek Trusted
15 Execution Environment) and AVF (Android Virtualization Framework) virtual
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | u-boot.yaml | 13 Device configuration is stored as a set of environment variables that are
27 Broadcom stores environment variables inside a U-Boot partition. They
|
| D | brcm,bcm947xx-cfe-partitions.yaml | 24 1) Bootloader with Broadcom's CFE (Common Firmware Environment)
33 CFE's environment variable "bootpartition" is used.
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | u-boot,env.yaml | 7 title: U-Boot environment variables layout
10 U-Boot uses environment variables to store device parameters and
17 Environment data can be stored on various storage entities, e.g.:
|
| /Documentation/arch/x86/ |
| D | intel_txt.rst | 15 - Measurement and verification of launched environment
112 tboot then verifies certain aspects of the environment (e.g. TPM NV
119 in the TXT environment, it is necessary to create a small VT-x
169 - Tboot will clean up the environment and disable TXT, then use the
174 measured environment upon resume. Once the TXT environment
182 and once the measured environment has been re-established, tboot
|
| /Documentation/devicetree/bindings/dma/ |
| D | qcom,bam-dma.yaml | 58 environment.
65 Indicates the active Execution Environment identifier (0-7) used in the
|
| /Documentation/userspace-api/ |
| D | no_new_privs.rst | 12 - The dynamic loader handles ``LD_*`` environment variables differently if
23 execution environment in a manner that persists across execve. Any task
|
| /Documentation/userspace-api/ebpf/ |
| D | index.rst | 6 eBPF is a kernel mechanism to provide a sandboxed runtime environment in the
|
| /Documentation/firmware_class/ |
| D | hotplug-script | 5 # Both $DEVPATH and $FIRMWARE are already provided in the environment.
|
| /Documentation/devicetree/bindings/input/ |
| D | ps2keyb-mouse-apbps2.txt | 5 Note: In the ordinary environment for the APBPS2 core, a LEON SPARC system,
|
| /Documentation/process/ |
| D | code-of-conduct.rst | 9 In the interest of fostering an open and welcoming environment, we as
19 Examples of behavior that contributes to creating a positive environment
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-grgpio.txt | 5 Note: In the ordinary environment for the GRGPIO core, a Leon SPARC system,
|
| /Documentation/security/keys/ |
| D | trusted-encrypted.rst | 21 environment for a specific use case. Since the kernel doesn't know what the
22 environment is, and there is no metric of trust, it is dependent on the
33 (2) TEE (Trusted Execution Environment: OP-TEE based on Arm TrustZone)
57 Fixed set of operations running in isolated execution environment.
62 environment verified via Secure/Trusted boot process.
66 Fixed set of operations running in isolated execution environment.
71 environment. Only basic blob key encryption is executed there.
|
| /Documentation/devicetree/bindings/peci/ |
| D | peci-controller.yaml | 13 PECI (Platform Environment Control Interface) is an interface that provides a
|
| /Documentation/devicetree/bindings/net/can/ |
| D | grcan.txt | 7 (the ordinary environment for GRCAN and GRHCAN). There are no dts files for
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-uevent.rst | 8 is the event contains environment attributes providing increased context for
21 The variables added to the uevent environment are:
|
| /Documentation/trace/coresight/ |
| D | coresight-perf.rst | 137 PERF_TEST_CORESIGHT_STATDIR environment variable before running perf
151 PERF_TEST_CORESIGHT_DATADIR environment variable such as::
156 You may wish to set these above environment variables if you wish to
|
123456789