> > But how can we be sure we're bug for bug and feature for feature > compatible with an arbitrary version of Windows? I got curious and > looked at the DSDT on my home PC, generic VIA KM266 chipset. Sure > enough: We aren't ever "sure". All I can say is that MS is the "defacto" implementation and that we attempt to both adhere to the ACPI spec and make some accommodations to the MS implementation (such as supporting the control method "implicit return") The NT/XP MS implementation is their best version with the fewest bugs, so this is the version that we are compatible with. Given this, and the fact that most iA32 platform BIOSs are developed and tested with XP, using the "Microsoft Windows NT" identification string seems to be the best way to go. By doing this, we have fixed at least several machines (maybe more) that were not working properly under Linux, and there haven't been any problems reported that I know of. Bob - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Tue Sep 14 11:23:07 2004
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:30 EST