Re: [ANNOUNCE] ACPI BIOS Guideline for Linux

It is not an ACPI specification violation that Linux
(and ACPICA) claim compatibility with the interfaces
advertised by one or multiple versions of Windows.

Yes, there are be cases where BIOS vendors will want
to know if the running version of Linux supports,
or does not support, an interface/feature.

We (the Linux community that maintain Linux/ACPI) are
eager to support them in this. However, the interface
needs to be sufficiently defined so that we know when
to _not_ advertise that feature.

eg. There are proposals for

_OSI("Linux-Needs ATI S3 video re-POST")
_OSI("Linux-Needs NVIDIA S3 video re-POST")
_OSI("Linux-Native IPMI Support")

and we'd compile these into Linux based on the capabilities
of the build. I'm sure that these would not be perfect --
as the BIOS would probably query these at _INI time before
the (likely loadable module) drivers that influence these
features would be loaded. So we'd probably have to build
them into the core based on the assumption that the driver
built with the core will actually get loaded.

But this is the kind of Linux-specific OSI string we can advertise,
and choose not to advertise -- depending on the build.

thanks,
-Len
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • (LONG) Looking for a few book-checkers
    ... Embedded Linux is harder to use than "regular desktop" ... Realtime characteristics are not as good as a "to the metal" ... master controller interfaces to several tiny subcontrollers which have ...
    (comp.arch.embedded)
  • Re: KDE
    ... Sid/Alan/Bruce/whatever also has severe ego issues. ... the GDE as much as he does, even if this only the case in his ... These interfaces, ... Linux OS and make them dependent on the technocrats. ...
    (comp.os.linux.setup)
  • Re: Servers just doent work (after followingthe troubleshooting page)
    ... It does have to do with the way Linux responds to certain network function calls that used to result in it using the wildcard socket. ... Changing the default and adding a new flag to get the default back would have been better. ... If it's going to be a platform-specific flag, it should be carefully arranged so that specifying *no* platform-specific flags gets you as close to the same behavior on all platforms. ... It is a platform-specific flag if the *effect* of binding to virtual interfaces is different on different platforms. ...
    (comp.protocols.time.ntp)
  • Re: Why so hard to setup hardware? Control panel?
    ... Different linux distrubitions have ... > different interfaces at the various levels of abstraction. ... SuSE have some customisations in their KDE ... I can get a much more consistant interface than I've ever seen in Windows. ...
    (comp.os.linux.setup)
  • Re: epoll and timeouts
    ... descriptors to internal socket structures is probably best. ... I don't think I understand why the map is better. ... thought-out interfaces. ... being added to Linux. ...
    (comp.unix.programmer)