On Fri, 2007-08-24 at 12:48 +0100, Matthew Garrett wrote:
> On Fri, Aug 24, 2007 at 09:48:45AM +0200, Thomas Renninger wrote:
> > I could imagine that distinguishing can be done through the OSI/_OS (or
> > similar, there are two ACPI functions to identify the OS, the old one is
> > called from OS telling the BIOS which OS is running, the other one is
> > called from BIOS and OS tells which OS are supported IIRC). Maybe if a
> > Vista string is in the game, the video extensions are armed...
> > Maybe there is a specific function the OS must call to make the video
> > extensions work.
>
> I'm not sure there's any especially compelling reason. As long as the
> platform-specific interfaces still work, there's no reason to prefer the
> ACPI interfaces.
There are some reasons:
- If the platform-specific interfaces do not work anymore, it's
already too late. E.g. we see this now for 10.3 with the ThinkPad
driver.
- If Vista is accessing those functions we should do this also
- Video module is rather untested and really needs some testing to
get the "Windows compatibility certificate". If Windows is really
making use of those functions extensively, this is the driver to
go for in future.
- Code cleanup: It would be great to rip out some duplicate code.
Especially the code size growth of the ThinkPad module which now
exceeds the 4000 line mark makes me a bit worry how this should
stay maintainable (imagine Henrique not doing all the good work
there anymore...).
Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
