| /openbmc/openbmc/ |
| H A D | setup | 110 vendors=""
115 if [[ ! "$vendors" =~ -$vendor- ]]; then
116 vendors="$vendors -$vendor-"
|
| /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/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/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/drivers/pci/controller/cadence/ |
| H A D | Kconfig | 32 vendors SoCs.
43 different vendors SoCs.
|
| /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
102 1. Common reboot causes across vendors can be consolidated to issue a unified
|
| /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/openbmc/meta-phosphor/scripts/ |
| H A D | generate-machine-list | 16 Systems which are actively developed and maintained by vendors are often
|
| /openbmc/linux/drivers/firmware/arm_ffa/ |
| H A D | Kconfig | 13 by an ecosystem of vendors from each other.
|
| /openbmc/u-boot/doc/SPI/ |
| H A D | status.txt | 13 - Common probe support for all supported flash vendors except, ramtron.
|
| /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-openembedded/meta-oe/recipes-graphics/libglvnd/ |
| H A D | libglvnd_1.7.0.bb | 2 OpenGL API calls between multiple vendors."
|
| /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 | 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 | kernel-driver-statement.rst | 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
|
| /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/openbmc/meta-phosphor/docs/ |
| H A D | supported-machines.md | 8 Systems which are actively developed and maintained by vendors are often
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | btusb.txt | 16 Also, vendors that use btusb may have device additional properties, e.g:
|
| H A D | nokia-bluetooth.txt | 5 vendors and modified device API. Those devices speak a protocol named H4+
|
| /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/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/usb/ |
| H A D | ohci.rst | 16 from vendors other than Intel and VIA generally use OHCI.
|
| /openbmc/linux/Documentation/devicetree/bindings/mtd/partitions/ |
| H A D | brcm,trx.txt | 5 most of the vendors building devices based on Broadcom's BCM47xx SoCs and is
|
| /openbmc/linux/Documentation/arch/xtensa/ |
| H A D | atomctl.rst | 30 Virtually all customers buy their memory controllers from vendors that
|