| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | cross-canadian.bbclass | 94 # Also need to handle multilib target vendors
95 vendors = d.getVar("CANADIANEXTRAVENDOR")
96 if not vendors:
97 vendors = all_multilib_tune_values(d, 'TARGET_VENDOR')
101 if origvendor not in vendors.split():
102 vendors = origvendor + " " + vendors
103 d.setVar("CANADIANEXTRAVENDOR", vendors)
|
| /openbmc/docs/designs/ |
| H A D | bmc-reboot-cause-update.md | 13 vendors to record different types of BMC reboot cause event logs. The purpose of
21 However, due to varying needs among different vendors, it’s not feasible to
59 1. Driver Provision by BMC Vendors:
102 1. Common reboot causes across vendors can be consolidated to issue a unified
|
| H A D | event-logging.md | 35 different vendors might use different strings to represent a critical
233 - The implementation must have a mechanism for vendors to be able to disable
630 As specified above, vendors must use their own identifiers in order to conform
633 implementation(s) will enable vendors to create their own events for downstream
635 repositories of error definitions. Vendors are responsible for ensuring their
639 One potential bad behavior on the part of vendors would be forking and modifying
640 `phosphor-dbus-interfaces` defined events. Vendors must not add their own events
736 - This does not cover vendors that may choose to branch for stabilization
742 - This does not cover vendors that build off HEAD and may deploy multiple
|
| /openbmc/openbmc/ |
| H A D | setup | 110 vendors=""
115 if [[ ! "$vendors" =~ -$vendor- ]]; then
116 vendors="$vendors -$vendor-"
|
| /openbmc/linux/drivers/pci/controller/cadence/ |
| H A D | Kconfig | 32 vendors SoCs.
43 different vendors SoCs.
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | arm-acpi.rst | 41 while DT explicitly does not support this. For hardware vendors, being
56 and an OS is important. Hardware vendors would not be required to implement
62 table as hardware vendors and other OS vendors. In fact, there is no
75 hardware vendors to take responsibility for power management behaviour without
78 ACPI is also important because hardware and OS vendors have already worked
83 server vendors need. Linux could potentially get there with DT, but doing so
85 the hardware vendors need, Microsoft won’t collaborate on DT, and hardware
86 vendors would still end up providing two completely separate firmware
358 reserving the name for later use. Other operating system vendors will
517 vendors that provide bad ACPI tables or violate the standards in some way.
|
| /openbmc/linux/Documentation/process/ |
| H A D | kernel-driver-statement.rst | 16 community. Vendors that provide closed-source kernel modules force their
17 customers to give up key Linux advantages or choose new vendors.
19 shared support benefits open source has to offer, we urge vendors to
|
| H A D | embargoed-hardware-issues.rst | 15 therefore need coordination across different OS vendors, distributions,
16 hardware vendors and other parties. For some of the issues, software
88 different OS vendors, distributors, hardware vendors and other parties.
156 industry, e.g. other OS vendors, HW vendors, etc.
|
| H A D | 1.Intro.rst | 63 vendors want to ensure that Linux supports their products well, making
64 those products attractive to Linux users. Embedded systems vendors, who
67 other software vendors who base their products on Linux have a clear
227 point, vendors whose code is in the mainline and well maintained will be
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | uadk-compression.rst | 9 which enables hardware accelerators from different vendors that support SVA to
21 UADK consists of UACCE, vendors' drivers, and an algorithm layer. UADK requires
23 IOMMU and SVA. Hardware accelerators from different vendors are registered as
25 vendors. A user can access the hardware accelerators by performing user-mode
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-soc | 37 limiting the possible number of vendors to 126. To expand
70 vendors. The format is "jep106:XXYY:ZZZZ" where XX is identity
|
| H A D | sysfs-class-scsi_host | 109 buffer. Different hardware(HW) vendors may have different
111 solved by allowing HW vendors to provide userland drivers and
|
| /openbmc/linux/tools/usb/usbip/libsrc/ |
| H A D | names.c | 77 static struct vendor *vendors[HASHSZ] = { NULL, }; variable
87 v = vendors[hashnum(vendorid)]; in names_vendor()
193 v = vendors[h]; in new_vendor()
202 v->next = vendors[h]; in new_vendor()
203 vendors[h] = v; in new_vendor()
|
| /openbmc/linux/drivers/misc/eeprom/ |
| H A D | Kconfig | 5 tristate "I2C EEPROMs / RAMs / ROMs from most vendors"
36 tristate "SPI EEPROMs (FRAMs) from most vendors"
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | sbrmi.rst | 18 The SMBus address is really 7 bits. Some vendors and the SMBus
20 bit as a write (0) making bit 0. Some vendors use only the 7 bits
|
| /openbmc/docs/designs/oem/google/ |
| H A D | root_of_trust.md | 88 version number. Most TPM2.0 vendors divide this into 4 fields each 2 bytes
91 numbers than the rest of the TPM vendors, reserving some bits and expressing
|
| /openbmc/linux/Documentation/hid/ |
| H A D | hid-sensor.rst | 10 hardware vendors to provide a consistent Plug And Play interface at the USB boundary,
12 could be reused between vendors, alleviating any need for the vendors to provide
|
| /openbmc/linux/drivers/net/wireless/intersil/orinoco/ |
| H A D | Kconfig | 77 PCI <-> PCMCIA bridge. Several vendors sell such adaptors so that
88 PCI <-> PCMCIA bridge. Several vendors sell such adaptors so that
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | booting.rst | 20 However, in order to make life easier to embedded board vendors, the kernel
29 code all sorts of tables. It also makes it more flexible for board vendors to do
|
| /openbmc/linux/drivers/firmware/arm_ffa/ |
| H A D | Kconfig | 13 by an ecosystem of vendors from each other.
|
| /openbmc/linux/fs/notify/fanotify/ |
| H A D | Kconfig | 24 use those files. This is used by some anti-malware vendors and by some
|
| /openbmc/openbmc/meta-phosphor/scripts/ |
| H A D | generate-machine-list | 16 Systems which are actively developed and maintained by vendors are often
|
| /openbmc/u-boot/doc/SPI/ |
| H A D | status.txt | 13 - Common probe support for all supported flash vendors except, ramtron.
|
| /openbmc/linux/Documentation/devicetree/bindings/i3c/ |
| H A D | mipi-i3c-hci.yaml | 20 host controller hardware implementations from multiple vendors.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/libglvnd/ |
| H A D | libglvnd_1.7.0.bb | 2 OpenGL API calls between multiple vendors."
|