Administrace komentářů

Moze to byt Harverom resp. BIOS-om Ja by som to tipol na DSDT tabulky v ACPI, ktora ak je kompilovana Microsoft kompilatorom je casto chybna a proti medzinarodnej norme pre ACPI. Kedze Microsoft vie, co v tabulke domrvil, tak to vie precitat svojim chybnym citacom, tak aby vo vysledku chyba nebola. Ty pouzivas distribucie, ktore citaju 100% korektne tabulky a pretosi neporadia s posranou tabulkou. Na posranu tabulku treba napr. openSUSE, ktory vie citat aj microsoftom posrane tabulky. Intel kompilator produkuje 100% korektne tabulky. To cim vyrobca hardvveru kompiluje ACPI tabulky je len na nom a na Tajvane a pouziva len MS kompilator...

While Microsoft uses its own proprietary, closed source ACPI compiler, Linux does make use of Intel's . The code base is used as ACPI parser and interpreter inside the kernel, but it also provides a lot of easy-to-use tools for general ACPI development and stability testing.

Most important for vendors is the iasl binary which can disassemble and recompile raw ACPI tables provided by the BIOS. It uses the same code base as the ACPI parser in the kernel. Therefore vendors should check whether their ACPI implementation sticks to the ACPI specification and works with the ACPICA tools (for an easy quick test, see below.

The Intel compiler is more strict. Warnings often lead to general ACPI BIOS errors that may also affect Microsoft Windows or other operating systems. Some may just point to ACPI specification violations which the Microsoft compiler allows. The Intel parser may also be able to cope with this code, but fixing such violations is easy in most cases and makes the ACPI BIOS implementation more robust against future operating system changes.

z Linux Weekly news