On Fri, Feb 22, 2008 at 03:07:42PM +0100, Thomas Renninger wrote: > So to what Windows version are we compatible?
Microsoft has been very good at keeping backwards compatibility for this functionality, so the obvious aim is to be compatible with the current version of Windows and all previous versions. If necessary, we can switch to compatibility modes depending on whether the firmware requests XP or Vista or whatever. > Do you want to remove lower versions at some time? No. > What about Longhorn or whatever coming up? We aim to be compatible with it. > Then these strings might branch into a server and a workstation Windows, > to which one do you want to stay compatible, both again? Whichever one the firmware asks for. > All this does not make sense and it does not work. It makes perfect sense and I've no reason to think it doesn't work. > All this is an advantage for vendors who do not care about Linux, but it > makes life really hard for vendors who want to support it. No! We have the choice between providing a benefit to a subset of vendors at the cost of never being able to fix bugs, or just making everything work. Given the choice between making everything work and making Lenovo work, I'll go for making everything work. > The _OSI interface is not thought for Linux kernel developers to stay > compatible with Windows. > It got invented for vendors being able to provide hot-fixes for their > BIOS for Operating Systems they are willing to support. No! _OSI is (according to the spec) there to enable vendors to support *features* provided by specific OSs, not to work around bugs in that OS. What does an _OSI of Linux mean? We don't have a well-defined feature set. We don't have a stable set of bugs. Our development model is inherently different from Windows, and providing this information just makes no sense. > So what should a vendor do if he has a BIOS hotfix for Windows 2003 > only. The fix workarounds an old W2003 AML bug. But this fix will break > Linux and Vista on his machine. For Vista he can take care, Linux will > break. And you are going to try to implement a workaround for an old > W2003 OS bug (after people got angry because their machine they bought > with Linux pre-loaded does not boot anymore after a BIOS update)... Fine. So we define different behaviour depending on whether the firmware asks for Vista or not. This isn't rocket science. -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
