Home
last modified time | relevance | path

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

12

/linux/Documentation/ABI/testing/
H A Dconfigfs-acpi40 - ASCII OEM identification
43 - ASCII OEM table identification
46 - OEM revision number
H A Dsysfs-amd-pmf8 if OEM BIOS passes a "flag" to PMF ACPI function (index 11 or 12)
H A Dsysfs-devices-platform-ipmi46 software to identify the unique application command, OEM
74 specification of functionality of the vendor (OEM)-specific
H A Dsysfs-firmware-dmi-entries8 cases where there are OEM extensions used.
/linux/drivers/platform/x86/uniwill/
H A DKconfig11 Uniwill x86 platforms, including many OEM laptops originally
33 like the lightbar, hwmon sensors and hotkeys. It also supports many OEM laptops
/linux/Documentation/admin-guide/acpi/
H A Dinitrd_table_override.rst64 # And increase the OEM Revision. For example, before modification:
72 # (similar Table Signature, and similar OEMID, and similar OEM Table ID)
73 # with a more recent OEM Revision, the platform table will be upgraded by
75 # (dissimilar Table Signature, or dissimilar OEMID, or dissimilar OEM Table
/linux/Documentation/firmware-guide/acpi/
H A Dosi.rst22 Linux runs on two groups of machines -- those that are tested by the OEM
41 What should an OEM do if they want to support Linux and Windows
45 In this case, the OEM should create custom ASL to be executed by the
51 _OSI("Linux-OEM-my_interface_name")
52 where 'OEM' is needed if this is an OEM-specific hook,
132 using it in untested BIOS flows. But some OEM's used _OSI("Linux")
/linux/drivers/platform/surface/
H A Dsurface3_power.c86 char OEM[SURFACE_3_STRLEN]; member
204 .OEM = "",
266 snprintf(bix->OEM, ARRAY_SIZE(bix->OEM), "%3pE", buf); in mshw0011_bix()
/linux/drivers/scsi/pcmcia/
H A DKconfig58 [I-O DATA (OEM) (version string: "IO DATA","CBSC16 ","1")]
60 [Kyusyu Matsushita Kotobuki (OEM)
/linux/net/ncsi/
H A DKconfig15 bool "Get NCSI OEM MAC Address"
/linux/Documentation/scsi/
H A DNinjaSCSI.rst100 # OEM
105 # OEM
H A Daacraid.rst19 PCI ID (pci.ids) OEM Product
163 Adaptec Unix OEM Product Group
/linux/drivers/media/usb/pwc/
H A DKconfig7 Say Y or M here if you want to use one of these Philips & OEM
/linux/drivers/platform/x86/amd/pmf/
H A DKconfig27 Enabling this option would give more debug information on the OEM fed
/linux/drivers/staging/nvec/
H A DKconfig46 tristate "Support for OEM specific functions on Compal PAZ00 based devices"
/linux/arch/arm/boot/dts/marvell/
H A Darmada-385-linksys-rango.dts83 /* AMD/Spansion S34ML02G2 256MiB, OEM Layout */
/linux/drivers/net/ethernet/natsemi/
H A DKconfig36 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
/linux/Documentation/admin-guide/media/
H A Dsaa7134-cardlist.rst418 - Asus Europa2 OEM
714 - Asus Europa Hybrid OEM
H A Dcx88-cardlist.rst238 - Shenzhen Tungsten Ages Tech TE-DTV-250 / Swann OEM
/linux/drivers/scsi/megaraid/
H A DKconfig.megaraid24 OEM Product Name VID :DID :SVID:SSID
/linux/drivers/iio/chemical/
H A DKconfig20 tristate "Atlas Scientific OEM SM sensors"
28 Atlas Scientific OEM SM sensors:
/linux/Documentation/driver-api/mmc/
H A Dmmc-dev-attrs.rst30 oemid OEM/Application ID (from CID Register)
/linux/Documentation/driver-api/
H A Dipmi.rst82 you want the whole panic string put into the event log using OEM
83 events, enable the 'Generate OEM events containing the panic string'
745 the 'Generate OEM events containing the panic string' option, you will
746 also get a bunch of OEM events holding the panic string.
756 * Event Data 1: 0xa1 (Runtime stop in OEM bytes 2 and 3)
764 Other OEM events have the following format:
767 * Record type (byte 2): 0xf0 (OEM non-timestamped)
774 Because you cannot send OEM events using the standard interface, this
/linux/Documentation/admin-guide/laptops/
H A Dalienware-wmi.rst17 is known to be used by the AWCC OEM application to control these features.
/linux/Documentation/hid/
H A Damd-sfh-hid.rst7 The solution is working well on several OEM products. AMD SFH uses HID over PCIe bus.

12