Lines Matching full:that
10 can evaluate that method, look to see if it supports 'XYZ'
14 that OSPM supports"
22 Linux runs on two groups of machines -- those that are tested by the OEM
23 to be compatible with Linux, and those that were never tested with Linux,
26 The larger group is the systems tested to run only Windows. Not only that,
30 Experience shows that taking untested paths through the BIOS
37 Windows to its list of _OSI strings. So it is possible that additional strings
39 But it is likely that they will all eventually be added.
52 via the linux-acpi@vger.kernel.org mailing list. When that patch
55 by the OS. Linux distributors can back-port that patch for Linux
56 pre-installs, and it will be included by all distributions that
63 the string when that support is added to the kernel.
65 That was easy. Read on, to find out how to do it wrong.
71 "object that evaluates to a string that identifies the operating system."
81 the BIOS could use _OS to enable devices that an OS
83 necessary to make the platform compatible with that pre-existing OS.
86 of every possible version of the OS that would run on it, and needed to know
94 that anybody would install those old operating systems
97 Linux answers "Microsoft Windows NT" to please that BIOS idiom.
98 That is the *only* viable strategy, as that is what modern Windows does,
109 An old OS that doesn't know about those extensions would answer FALSE,
112 For an OS-specific interface, the ACPI spec said that the BIOS and the OS
125 a BIOS that has been tested only with that _OSI returning TRUE.
139 for all BIOS's that invoke it.
144 ACPI BIOS that are tested on Windows machines. There is a real risk
145 of over-stating that compatibility; but the alternative has often been
146 catastrophic failure resulting from the BIOS taking paths that
163 _REV = 4, that support broke.
167 to reflect that _REV is deprecated, and always returns 2.