Home
last modified time | relevance | path

Searched refs:vendors (Results 1 – 25 of 85) sorted by relevance

1234

/linux/tools/usb/usbip/libsrc/
A Dnames.c77 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()
/linux/drivers/pci/controller/cadence/
A DKconfig32 vendors SoCs.
43 different vendors SoCs.
/linux/Documentation/hwmon/
A Dsbrmi.rst18 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
/linux/Documentation/process/
A Dembargoed-hardware-issues.rst15 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.
A Dkernel-driver-statement.rst17 customers to give up key Linux advantages or choose new vendors.
19 shared support benefits open source has to offer, we urge vendors to
A D1.Intro.rst63 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
/linux/Documentation/arm64/
A Darm-acpi.rst40 while DT explicitly does not support this. For hardware vendors, being
55 and an OS is important. Hardware vendors would not be required to implement
61 table as hardware vendors and other OS vendors. In fact, there is no
74 hardware vendors to take responsibility for power management behaviour without
77 ACPI is also important because hardware and OS vendors have already worked
82 server vendors need. Linux could potentially get there with DT, but doing so
84 the hardware vendors need, Microsoft won’t collaborate on DT, and hardware
85 vendors would still end up providing two completely separate firmware
303 reserving the name for later use. Other operating system vendors will
462 vendors that provide bad ACPI tables or violate the standards in some way.
/linux/drivers/firmware/arm_ffa/
A DKconfig13 by an ecosystem of vendors from each other.
/linux/Documentation/devicetree/bindings/gnss/
A Dmediatek.txt4 vendors and can use a UART interface.
A Dsirfstar.txt4 vendors and can use UART, SPI or I2C interfaces.
/linux/Documentation/ABI/testing/
A Dsysfs-devices-soc37 limiting the possible number of vendors to 126. To expand
70 vendors. The format is "jep106:XXYY:ZZZZ" where XX is identity
A Dsysfs-class-scsi_host109 buffer. Different hardware(HW) vendors may have different
111 solved by allowing HW vendors to provide userland drivers and
/linux/fs/notify/fanotify/
A DKconfig24 use those files. This is used by some anti-malware vendors and by some
/linux/Documentation/devicetree/bindings/i3c/
A Dmipi-i3c-hci.yaml20 host controller hardware implementations from multiple vendors.
/linux/Documentation/devicetree/bindings/net/
A Dbtusb.txt16 Also, vendors that use btusb may have device additional properties, e.g:
A Dnokia-bluetooth.txt5 vendors and modified device API. Those devices speak a protocol named H4+
/linux/drivers/misc/eeprom/
A DKconfig5 tristate "I2C EEPROMs / RAMs / ROMs from most vendors"
35 tristate "SPI EEPROMs (FRAMs) from most vendors"
/linux/Documentation/hid/
A Dhid-sensor.rst10 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
/linux/Documentation/devicetree/bindings/mtd/partitions/
A Dbrcm,trx.txt5 most of the vendors building devices based on Broadcom's BCM47xx SoCs and is
/linux/Documentation/usb/
A Dohci.rst16 from vendors other than Intel and VIA generally use OHCI.
/linux/Documentation/xtensa/
A Datomctl.rst30 Virtually all customers buy their memory controllers from vendors that
/linux/tools/thermal/tmon/
A DREADME9 As hardware vendors cope with the thermal constraints on their products, more
/linux/drivers/net/wireless/intersil/orinoco/
A DKconfig77 PCI <-> PCMCIA bridge. Several vendors sell such adaptors so that
88 PCI <-> PCMCIA bridge. Several vendors sell such adaptors so that
/linux/Documentation/powerpc/
A Dbooting.rst20 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
/linux/Documentation/driver-api/
A Dhsi.rst10 implemented by multiple vendors since then.

Completed in 27 milliseconds

1234