| /openbmc/u-boot/board/coreboot/coreboot/ |
| H A D | Kconfig | 23 hex "Board specific Cache-As-RAM (CAR) address"
26 This option specifies the board specific Cache-As-RAM (CAR) address.
29 hex "Board specific Cache-As-RAM (CAR) size"
32 This option specifies the board specific Cache-As-RAM (CAR) size.
|
| /openbmc/openbmc/poky/meta/conf/machine/include/arm/ |
| H A D | README | 11 A small set of ARM specific variables have been defined to allow
25 ARMPKGSFX_THUMB - This is the thumb specific suffix. Curently it is
28 ARMPKGSFX_DSP - This is the DSP specific suffix. Currently this is set
31 ARMPKGSFX_EABI - This is the eabi specific suffix. There are currently
36 ARMPKGSFX_ENDIAN - This is the endian specific suffix. It is defined in
39 ARMPKGSFX_FPU - This is the FPU specific suffix. The suffix indicates
40 specific FPU optimizations. 'vfp' and 'neon' are both defined.
|
| /openbmc/docs/ |
| H A D | hw-vendor-repos-policy.md | 25 Both hardware-specific and vendor-specific repositories should meet the
63 Note that when a recipe is non-OpenBMC specific, but useful to OpenBMC, it
70 1. A function that is specific to the vendor hardware
71 - For example, PECI, FSI, hardware diagnostics (specific to the processor)
72 2. A device attached to the BMC (MCTP/PLDM/I2C/...) that is specific to the
75 To add a hardware specific repository to OpenBMC, it should meet the following
78 1. If it requires specific kernel APIs, they are available or in progress via
87 A vendor-specific feature is defined as one of the following:
89 1. A vendor-specific data format or protocol
92 2. A function that requires a specific hardware vendor feature
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/tests/ |
| H A D | qemu-img-bitmaps | 93 _img_info --format-specific | _filter_irrelevant_img_info
103 _img_info --format-specific | _filter_irrelevant_img_info
112 _img_info --format-specific --backing-chain | _filter_irrelevant_img_info
142 _img_info --format-specific | _filter_irrelevant_img_info
147 TEST_IMG="$TEST_IMG.copy" _img_info --format-specific \
153 TEST_IMG="$TEST_IMG.copy" _img_info --format-specific \
161 TEST_IMG="$TEST_IMG.copy" _img_info --format-specific \
|
| H A D | qemu-img-bitmaps.out | 28 Format specific information:
44 Format specific information:
69 Format specific information:
90 Format specific information:
127 Format specific information:
157 Format specific information:
170 Format specific information:
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | virtio.rst | 18 transport specific state (msix vectors, indicators, ...)
43 - save transport-specific
50 - save transport-specific
53 - save device-specific
80 - load transport-specific
87 - load transport-specific
91 - load device-specific
114 added to the core for compatibility reasons. If transport or device specific
|
| /openbmc/u-boot/arch/riscv/cpu/ax25/ |
| H A D | Kconfig | 4 Run U-Boot on AndeStar V5 platforms and use some specific features
10 bool "AndeStar V5 families specific cache support"
12 Provide Andes Technology AndeStar V5 families specific cache support.
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | openbmc_message_registry.readmefirst.md | 9 1. Messages should not be specific to a piece or type of hardware. Generally
11 message strings, unless that behavior is specific to that particular piece of
13 MemoryECCError (ECC is specific to memory, therefore class specific is
16 2. Messages should not use any proprietary, copyright, or company-specific
29 5. If you are changing this in your own downstream company-specific fork, please
|
| /openbmc/u-boot/board/xilinx/zynqmp/ |
| H A D | Kconfig | 8 bool "Enable ZynqMP specific commands"
11 Enable ZynqMP specific commands like "zynqmp secure"
13 The secure image is a xilinx specific BOOT.BIN with
|
| /openbmc/pldm/docs/ |
| H A D | pdr_implementation.md | 4 they can vary across platforms and systems. For this reason, platform specific
5 PDR information is encoded in platform specific JSON files. JSON files must be
8 additional processing (apart from PDR creation) for specific PDR types, for eg
12 PDR repository. Platform specific PDR modifications would likely just result in
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/config_file/ |
| H A D | README.md | 8 - [System-Specific Configuration Files](#system-specific-configuration-files)
44 Config files are often system-specific. Each system type usually has a different
47 System-specific config files can support isolating which rail caused a power
56 - If the option is false, a system-specific config file is used.
60 System-specific config files are found using the
68 system types. The types are ordered from most specific to least specific.
77 compatible system types. It searches from most specific to least specific. The
|
| /openbmc/u-boot/drivers/fpga/ |
| H A D | Kconfig | 13 Enable Altera FPGA specific functions which includes bitstream
28 Say Y here to enable the Altera Cyclone II FPGA specific driver
39 Say Y here to enable the Altera Stratix 10 FPGA specific driver
49 Enable Xilinx FPGA specific functions which includes bitstream
78 specific for Aspeed FPGA devices
|
| /openbmc/u-boot/board/xilinx/zynq/ |
| H A D | Kconfig | 8 bool "Enable Zynq specific commands"
11 Enables Zynq specific commands.
28 The secure image is a xilinx specific BOOT.BIN with
|
| /openbmc/u-boot/doc/ |
| H A D | README.AMCC-eval-boards-cleanup | 17 o Merged board specific flash drivers to common flash driver:
26 o Moved EBC configuration from board specific asm-file "init.S"
27 using defines in board configuration file. No board specific
|
| /openbmc/u-boot/board/intel/galileo/ |
| H A D | dsdt.asl | 8 /* platform specific */
11 /* board specific */
|
| /openbmc/u-boot/board/intel/minnowmax/ |
| H A D | dsdt.asl | 8 /* platform specific */
11 /* board specific */
|
| /openbmc/u-boot/board/advantech/som-db5800-som-6867/ |
| H A D | dsdt.asl | 8 /* platform specific */
11 /* board specific */
|
| /openbmc/u-boot/board/intel/bayleybay/ |
| H A D | dsdt.asl | 8 /* platform specific */
11 /* board specific */
|
| /openbmc/u-boot/board/dfi/dfi-bt700/ |
| H A D | dsdt.asl | 8 /* platform specific */
11 /* board specific */
|
| /openbmc/u-boot/board/congatec/conga-qeval20-qa3-e3845/ |
| H A D | dsdt.asl | 8 /* platform specific */
11 /* board specific */
|
| /openbmc/bmcweb/ |
| H A D | .gitignore | 13 # project specific
24 # User-specific stuff
31 # AWS User-specific
152 # PyDev specific (Python IDE for Eclipse)
155 # CDT-specific (C/C++ Development Tooling)
164 # PDT-specific (PHP Development Tools)
186 # Scala IDE specific (Scala & Java development for Eclipse)
226 sanitycheckcpp.cc # C++ specific
227 sanitycheckcpp.exe # C++ specific
|
| /openbmc/docs/designs/ |
| H A D | psu-firmware-update.md | 53 avoid power loss. This shall be handled by PSU vendor-specific tools, but not in
56 Note: The "vendor-specific" referred below is the PSU vendor-specific.
58 So the below checks are optional and expected to be handled by vendor-specific
83 vendor-specific purpose, e.g. to indicate the PSU model.
102 its related vendor-specific tools.
103 - The service will find the matched vendor-specific tool to perform the code
104 update. For example, if a vendor specific tool `foo` is configured in
113 4. The vendor-specific tool shall run all the checks it needs to be run, before
116 5. When the vendor-specific tool returns errors, the PSU update will be aborted
137 3. If PSU update is needed, the service will find the matched vendor-specific
[all …]
|
| /openbmc/openbmc/poky/meta/conf/machine/include/ |
| H A D | README | 38 specific tune. This is a list of features that a tune support, each
44 ABIEXTENSION - An ABI extension may be specified by a specific feature
47 ABIEXTENSION = "eabi" in the arm case, or appended to in specific tune
55 TUNE_ARCH - The GNU canonical arch for a specific architecture. i.e.
57 configure. TUNE_ARCH definitions are specific to a given architecture.
63 Similarly to TUNE_ARCH, the definition of TUNE_PKGARCH is specific to
73 that are compatible with this specific tune. The package arch of this
78 architecture specific floating point. This is synchronized with the
82 BASE_LIB:tune-<tune> - The "/lib" location for a specific ABI. This is
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 082 | 62 _img_info --format-specific
66 _img_info --format-specific
121 TEST_IMG="${TEST_IMG}.base" _img_info --format-specific
125 TEST_IMG="${TEST_IMG}.base" _img_info --format-specific
176 _img_info --format-specific
180 _img_info --format-specific
184 _img_info --format-specific
|
| /openbmc/openbmc/poky/meta/conf/machine/include/powerpc/ |
| H A D | tune-ppc476.inc | 5 TUNEVALID[ppc476] = "Enable ppc476 specific processor optimizations"
13 # glibc configure options to get 476 specific library (for sqrt)
|