| /openbmc/qemu/linux-user/sparc/ |
| H A D | termbits.h | 96 #define TARGET_PAGEOUT 0x00010000 /* SUNOS specific */
97 #define TARGET_WRAP 0x00020000 /* SUNOS specific */
202 //#define __TIOCHPCL _IO('t', 2) /* SunOS Specific */
203 //#define __TIOCMODG _IOR('t', 3, int) /* SunOS Specific */
204 //#define __TIOCMODS _IOW('t', 4, int) /* SunOS Specific */
205 //#define __TIOCGETP _IOR('t', 8, struct sgttyb) /* SunOS Specific */
206 //#define __TIOCSETP _IOW('t', 9, struct sgttyb) /* SunOS Specific */
207 //#define __TIOCSETN _IOW('t', 10, struct sgttyb) /* SunOS Specific */
210 //#define __TIOCFLUSH _IOW('t', 16, int) /* SunOS Specific */
211 //#define __TIOCSETC _IOW('t', 17, struct tchars) /* SunOS Specific */
[all …]
|
| /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
66 ### Hardware Specific Feature
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
85 ### Vendor Specific Feature
87 A vendor-specific feature is defined as one of the following:
[all …]
|
| H A D | meta-layer-guidelines.md | 3 While most of these could be called "rules", in specific scenarios might be
66 autotools to meson, in pursuit of other goals. Having tool-specific
109 ## Meta layers should not point to OpenBMC specific repositories outside of <https://github.com/ope…
111 **What defines an OpenBMC specific repository?**
113 Generally an OpenBMC specific repository is something that does any of the
118 - Relies on OpenBMC specific layouts, configuration information to accomplish
127 OpenBMC-specific code outside of github limits the ability of the project to do
153 Point SRCREV to a specific commit of the repository, and increase the revision
166 Meta-layers are often set up where company-specific developers have merge
168 conform to broader expectations, without oversight, and lead to company-specific
|
| /openbmc/u-boot/include/ |
| H A D | spl_gpio.h | 17 * number is encoded in an unsigned int by an SoC-specific means. Pull
18 * values are also SoC-specific.
24 * often specific to a particular SoC generation. This allows the GPIO
30 * encoding is SoC-specific.
37 * @gpio: GPIO to adjust (SoC-specific)
38 * @pull: Pull value (SoC-specific)
47 * @gpio: GPIO to adjust (SoC-specific)
57 * @gpio: GPIO to adjust (SoC-specific)
|
| H A D | video_osd.h | 29 * either a generic form (by specifying a string, a driver-specific color value
31 * driver-specific form (by specifying "raw" driver-specific data to display at
56 * set_mem() - Write driver-specific text data to OSD screen
58 * The passed data are device-specific, and it's up to the driver how
60 * driver-specific; most likely the given data will be written to the
68 * will write the device-specific text data "A" to the positions (0, 0)
71 * Device-specific text data may, e.g. be a special encoding of glyphs
77 * @buf: Array containing device-specific data to write to the
108 * driver-specific, and possible values should be defined
135 * The passed data are device-specific, and it's up to the driver how to
[all …]
|
| /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/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/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/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/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/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/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/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 | 22 general error when a pgood fault occurs. No specific rail will be identified.
33 A config file is normally system-specific. Each system type usually has a
42 system types. The types are ordered from most specific to least specific.
51 matches one of these compatible system types. It searches from most specific to
52 least specific. The first config file found, if any, will be used.
|
| /openbmc/qemu/include/accel/ |
| H A D | accel-cpu-target.h | 3 * This header is used only by target-specific code.
15 * This header is used to define new accelerator-specific target-specific
17 * It uses CPU_RESOLVING_TYPE, so this is clearly target-specific.
|
| /openbmc/u-boot/doc/device-tree-bindings/exynos/ |
| H A D | dwmmc.txt | 10 SOC specific and Board specific properties are channel specific.
12 Required SoC Specific Properties:
22 Required Board Specific Properties:
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | kickstart.rst | 81 - ``--source``: This option is a Wic-specific option that names the
141 - ``--align (in KBytes)``: This option is a Wic-specific option that
144 - ``--offset``: This option is a Wic-specific option that
152 - ``--no-table``: This option is a Wic-specific option. Using the
157 - ``--exclude-path``: This option is a Wic-specific option that
161 - ``--extra-space``: This option is a Wic-specific option that adds
169 - ``--overhead-factor``: This option is a Wic-specific option that
174 - ``--part-name``: This option is a Wic-specific option that
177 - ``--part-type``: This option is a Wic-specific option that
182 - ``--use-uuid``: This option is a Wic-specific option that causes
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | PowerSupplyRedundancy.interface.yaml | 17 Rotation algorithm use for cold redundancy. 0 is BMC Specific, 1 is
18 User Specific.
28 Specific, and rotation is enabled, BMC will change PSU rank order
51 With BMC Specific algorithm, when rotation happen, BMC will add
56 With User Specific algorithm, user need to set the
|
| /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/u-boot/doc/ |
| H A D | README.fsl-hwconfig | 1 Freescale-specific 'hwconfig' options.
3 This file documents Freescale-specific key:value pairs for the 'hwconfig'
7 Specific to the P1022DS reference board.
24 Specific to boards have USB controller
|
| /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/openbmc/meta-nuvoton/recipes-nuvoton/program-edid/program-edid/ |
| H A D | edid.json | 147 "Manufacturer specific display mode 1": false,
148 "Manufacturer specific display mode 2": false,
149 "Manufacturer specific display mode 3": false,
150 "Manufacturer specific display mode 4": false,
151 "Manufacturer specific display mode 5": false,
152 "Manufacturer specific display mode 6": false,
153 "Manufacturer specific display mode 7": false
|
| /openbmc/qemu/include/hw/core/ |
| H A D | sysemu-cpu-ops.h | 2 * CPU operations specific to system emulation
16 * struct SysemuCPUOps: System operations specific to a CPU class
56 * @write_elf32_note: Callback for writing a CPU-specific ELF note to a
62 * @write_elf64_note: Callback for writing a CPU-specific ELF note to a
68 * @write_elf32_qemunote: Callback for writing a CPU- and QEMU-specific ELF
74 * @write_elf64_qemunote: Callback for writing a CPU- and QEMU-specific ELF
|
| /openbmc/u-boot/arch/arm/mach-exynos/include/mach/ |
| H A D | board.h | 11 * Exynos baord specific changes for
17 * Exynos board specific changes for
23 * Exynos board specific changes for
|
| /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
|