On Fri, 01 Aug 2008, Len Brown wrote:
quoted text
> It is better to expose ourselves to the known tested Windows functionality
> -- even if it seems arbitrary, at least it is tested.  The !Windows case
> results in running _completely_ untested BIOS code.

Actually, we should masquerade properly as the latest Windows version
available for that machine, then.  AFAIK, Windows does not set ALL the OSI
strings, just one.  We ARE running untested code in some BIOSes because of
it.

Maybe it would be better if every ACPICA-using OS defined a
_OSI(NotWindows), plus the relevant Windows OSI string they want to support,
and Intel would send word that this string is to be used ONLY to disable all
Windows bug workarounds, not to activate or deactivate any specific
functionality?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/