Searched full:specific (Results 1 – 25 of 6004) sorted by relevance
12345678910>>...241
| /openbmc/linux/drivers/ufs/host/ |
| D | Kconfig | |
| /openbmc/linux/arch/sparc/include/uapi/asm/ |
| D | ioctls.h | |
| /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 …]
|
| /openbmc/linux/include/linux/mtd/ |
| D | platnand.h | |
| /openbmc/linux/Documentation/devicetree/bindings/hwlock/ |
| D | hwlock.txt | |
| /openbmc/linux/Documentation/arch/sh/ |
| D | new-machine.rst | |
| /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/linux/drivers/usb/musb/ |
| D | musb_io.h | |
| /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/linux/drivers/staging/vc04_services/vchiq-mmal/ |
| D | mmal-msg-format.h | |
| /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/linux/include/uapi/linux/ |
| D | chio.h | |
| /openbmc/linux/drivers/media/platform/microchip/ |
| D | microchip-isc-regs.h | |
| /openbmc/linux/drivers/staging/media/deprecated/atmel/ |
| D | atmel-isc-regs.h | |
| /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/linux/drivers/clk/meson/ |
| D | clk-regmap.h | |
| /openbmc/linux/drivers/thunderbolt/ |
| D | nhi.h | |
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-tx.rst | |
| /openbmc/linux/Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | |
| /openbmc/linux/drivers/bcma/ |
| D | README | |
| /openbmc/linux/Documentation/driver-api/usb/ |
| D | typec_bus.rst | |
| /openbmc/linux/Documentation/driver-api/ |
| D | vfio-pci-device-specific-driver-acceptance.rst | |
| /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
|
12345678910>>...241