Home
last modified time | relevance | path

Searched refs:OEM (Results 1 – 25 of 51) sorted by relevance

123

/Linux-v4.19/Documentation/ABI/testing/
Dconfigfs-acpi32 oem_id - ASCII OEM identification
33 oem_table_id - ASCII OEM table identification
34 oem_revision - OEM revision number
Dsysfs-devices-platform-ipmi46 software to identify the unique application command, OEM
74 specification of functionality of the vendor (OEM)-specific
/Linux-v4.19/Documentation/acpi/
Dosi.txt19 Linux runs on two groups of machines -- those that are tested by the OEM
38 What should an OEM do if they want to support Linux and Windows
43 _OSI("Linux-OEM-my_interface_name")
44 where 'OEM' is needed if this is an OEM-specific hook,
48 In addition, the OEM should send a patch to upstream Linux
51 on the OEM's system uses _OSI to ask if the interface is supported
55 they can also add an acpi_osi=Linux-OEM-my_interface_name
132 using it in untested BIOS flows. But some OEM's used _OSI("Linux")
Dinitrd_table_override.txt58 # And increase the OEM Revision. For example, before modification:
66 # (similar Table Signature, and similar OEMID, and similar OEM Table ID)
67 # with a more recent OEM Revision, the platform table will be upgraded by
69 # (dissimilar Table Signature, or dissimilar OEMID, or dissimilar OEM Table
/Linux-v4.19/Documentation/hwmon/
Dftsteutates26 ftp://ftp.ts.fujitsu.com/pub/Mainboard-OEM-Sales/Services/Software&Tools/Linux_SystemMonitoring&Wat…
27 ftp://ftp.ts.fujitsu.com/pub/Mainboard-OEM-Sales/Services/Software&Tools/Linux_SystemMonitoring&Wat…
/Linux-v4.19/drivers/iio/chemical/
DKconfig8 tristate "Atlas Scientific OEM SM sensors"
16 Atlas Scientific OEM SM sensors:
/Linux-v4.19/drivers/scsi/pcmcia/
DKconfig45 [I-O DATA (OEM) (version string: "IO DATA","CBSC16 ","1")]
47 [Kyusyu Matsushita Kotobuki (OEM)
/Linux-v4.19/Documentation/devicetree/bindings/iio/chemical/
Datlas,ec-sm.txt1 * Atlas Scientific EC-SM OEM sensor
Datlas,orp-sm.txt1 * Atlas Scientific ORP-SM OEM sensor
Datlas,ph-sm.txt1 * Atlas Scientific pH-SM OEM sensor
/Linux-v4.19/drivers/char/ipmi/
DKconfig36 bool 'Generate OEM events containing the panic string'
40 by default, generate IPMI OEM type f0 events holding the IPMB
44 usage for an OEM event. You can fetch these events and use the
/Linux-v4.19/Documentation/scsi/
DNinjaSCSI.txt78 # OEM
83 # OEM
Daacraid.txt13 PCI ID (pci.ids) OEM Product
139 Adaptec Unix OEM Product Group
/Linux-v4.19/drivers/media/usb/pwc/
DKconfig6 Say Y or M here if you want to use one of these Philips & OEM
/Linux-v4.19/Documentation/devicetree/bindings/fuse/
Dnvidia,tegra20-fuse.txt15 the location of the spare (OEM programmable) bits and the location of
/Linux-v4.19/drivers/staging/nvec/
DKconfig45 tristate "Support for OEM specific functions on Compal PAZ00 based devices"
/Linux-v4.19/drivers/net/wireless/cisco/
DKconfig49 supports OEM of Cisco such as the DELL TrueMobile 4800 and Xircom
/Linux-v4.19/arch/arm/boot/dts/
Darmada-385-linksys-rango.dts83 /* AMD/Spansion S34ML02G2 256MiB, OEM Layout */
Dlpc3250-ea3250.dts88 /* LEDs on OEM Board */
/Linux-v4.19/drivers/scsi/megaraid/
DKconfig.megaraid23 OEM Product Name VID :DID :SVID:SSID
/Linux-v4.19/Documentation/isdn/
DREADME.hfc-pci2 for many OEM cards using this chips.
/Linux-v4.19/drivers/net/ethernet/natsemi/
DKconfig35 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
/Linux-v4.19/Documentation/media/v4l-drivers/
Dsaa7134-cardlist.rst416 - Asus Europa2 OEM
712 - Asus Europa Hybrid OEM
/Linux-v4.19/Documentation/
DIPMI.txt82 you want the whole panic string put into the event log using OEM
83 events, enable the 'Generate OEM events containing the panic string'
684 the 'Generate OEM events containing the panic string' option, you will
685 also get a bunch of OEM events holding the panic string.
695 * Event Data 1: 0xa1 (Runtime stop in OEM bytes 2 and 3)
703 Other OEM events have the following format:
706 * Record type (byte 2): 0xf0 (OEM non-timestamped)
713 Because you cannot send OEM events using the standard interface, this
/Linux-v4.19/Documentation/mmc/
Dmmc-dev-attrs.txt24 oemid OEM/Application ID (from CID Register)

123