ACPI diff: Let's expand upon our list of lies! :-)

2014-03-13 Thread Bryan Steele 
It seems Microsoft has a document in an annoying format (DOCX) that
contains a list of their _OSI strings, so, let's pretend to be Windows 8
and Windows 8.1 if the firmware asks us. This could avoid buggy AML
paths on systems that don't ship with Windows 7 anymore.

http://webcache.googleusercontent.com/search?q=cache:IQGiRbuEXSUJ:download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/WinACPI_OSI.docx+

-Bryan.

Index: dsdt.c
===
RCS file: /cvs/src/sys/dev/acpi/dsdt.c,v
retrieving revision 1.205
diff -u -p -r1.205 dsdt.c
--- dev/acpi/dsdt.c 12 Dec 2013 20:56:01 -  1.205
+++ dev/acpi/dsdt.c 13 Mar 2014 17:06:35 -
@@ -1510,6 +1510,8 @@ char *aml_valid_osi[] = {
Windows 2001 SP4,
Windows 2006,
Windows 2009,
+   Windows 2012,
+   Windows 2013,
NULL
 };

Re: ACPI diff: Let's expand upon our list of lies! :-)

2014-03-13 Thread Mark Kettenis 
 Date: Thu, 13 Mar 2014 13:23:40 -0400
 From: Bryan Steele bry...@openbsd.org
 
 It seems Microsoft has a document in an annoying format (DOCX) that
 contains a list of their _OSI strings, so, let's pretend to be Windows 8
 and Windows 8.1 if the firmware asks us. This could avoid buggy AML
 paths on systems that don't ship with Windows 7 anymore.
 
 http://webcache.googleusercontent.com/search?q=cache:IQGiRbuEXSUJ:download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/WinACPI_OSI.docx+
 
 -Bryan.

This will potentially screw up the brighness buttons on some machines.
Let's go ahead with it and see what happens ;)

 Index: dsdt.c
 ===
 RCS file: /cvs/src/sys/dev/acpi/dsdt.c,v
 retrieving revision 1.205
 diff -u -p -r1.205 dsdt.c
 --- dev/acpi/dsdt.c   12 Dec 2013 20:56:01 -  1.205
 +++ dev/acpi/dsdt.c   13 Mar 2014 17:06:35 -
 @@ -1510,6 +1510,8 @@ char *aml_valid_osi[] = {
   Windows 2001 SP4,
   Windows 2006,
   Windows 2009,
 + Windows 2012,
 + Windows 2013,
   NULL
  };

Re: ACPI diff: Let's expand upon our list of lies! :-)

2014-03-13 Thread Theo de Raadt 
I agree as well.

  It seems Microsoft has a document in an annoying format (DOCX) that
  contains a list of their _OSI strings, so, let's pretend to be Windows 8
  and Windows 8.1 if the firmware asks us. This could avoid buggy AML
  paths on systems that don't ship with Windows 7 anymore.
  
  http://webcache.googleusercontent.com/search?q=cache:IQGiRbuEXSUJ:download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/WinACPI_OSI.docx+
  
  -Bryan.
 
 This will potentially screw up the brighness buttons on some machines.
 Let's go ahead with it and see what happens ;)
 
  Index: dsdt.c
  ===
  RCS file: /cvs/src/sys/dev/acpi/dsdt.c,v
  retrieving revision 1.205
  diff -u -p -r1.205 dsdt.c
  --- dev/acpi/dsdt.c 12 Dec 2013 20:56:01 -  1.205
  +++ dev/acpi/dsdt.c 13 Mar 2014 17:06:35 -
  @@ -1510,6 +1510,8 @@ char *aml_valid_osi[] = {
  Windows 2001 SP4,
  Windows 2006,
  Windows 2009,
  +   Windows 2012,
  +   Windows 2013,
  NULL
   };