Lines Matching +full:string +full:- +full:support

1 .. SPDX-License-Identifier: GPL-2.0
22 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
50 In the past the kernel used to support something like:
51 _OSI("Linux-OEM-my_interface_name")
52 where 'OEM' is needed if this is an OEM-specific hook,
54 quirk, a bug, or a bug-fix.
60 any custom Linux-* strings by default.
68 "object that evaluates to a string that identifies the operating system."
71 interpreter in the kernel would return to it a string identifying the OS:
79 might support, or enable quirks or bug workarounds
80 necessary to make the platform compatible with that pre-existing OS.
86 "do you support a specific interface", and thus in ACPI 3.0,
90 _OS "Microsoft Windows NT", though it seems somewhat far-fetched
101 With _OSI, the *BIOS* provides the string describing an interface,
109 For an OS-specific interface, the ACPI spec said that the BIOS and the OS
110 were to agree on a string of the form such as "Windows-interface_name".
113 not as designed, but as a direct replacement for _OS -- identifying
128 Not to be out-done, the Linux community made things worse by returning TRUE
133 in tested flows to support real Linux features.  In 2009, Linux
142 of over-stating that compatibility; but the alternative has often been
150 to support Linux and Windows differences in the same BIOS.
160 _REV = 4, that support broke.
163 from mid-2015 onward.  The ACPI specification will also be updated
175 Just like on Windows-tested platforms, this strategy has risks.
177 Starting in Linux-3.18, the kernel answered YES to _OSI("Darwin")
178 for the purpose of enabling Mac Thunderbolt support.  Further,
183 The Linux-3.18 change in default caused power regressions on Mac
185 the default via cmdline "acpi_osi=!Darwin".  Linux-4.7 fixed
187 we hope to see Mac Thunderbolt power management support in Linux-4.11.