Re: ACPI quirk for ASUS CUR-DLS

["Jared D. McNeill" <jmcneill%invisible.ca@localhost>]

On Sun, 18 May 2008, Pierre Pronchery wrote:
> I had the curiosity to check what Linux does in this regard. It turns
> out they have a specific ACPI quirk, that disables the use of ACPI
> altogether on this board:
>
> arch/i386/kernel/dmi_scan.c, from Linux 2.4.36.2:
> 902         { force_acpi_ht, "ASUS CUR-DLS", {
> 903                         MATCH(DMI_BOARD_VENDOR, "ASUSTeK Computer INC."),
> 904                         MATCH(DMI_BOARD_NAME, "CUR-DLS"),
> 905                         NO_MATCH, NO_MATCH }},

This is matching on information from the DMI tables..

> And in fact, booting the 4.0 GENERIC.MP kernel with "disable acpi" works
> perfectly so far. Therefore, I figured I would try to add a
> quirk for NetBSD. This seems to be done in dev/acpi/acpi_quirks.c, where
> I added this:
>
> 65         { ACPI_TABLE_DSDT, "ASUS  ", 0x00000000, AQ_GTE, "CUR-DLS ",
> 66           ACPI_QUIRK_BROKEN },

.. and this matches against information in the DSDT.

> But this does not fix the problem: the early AML breakpoint is still
> hit, and then ACPI still seems to be used. How can I determine if this
> entry is correct?

If you would like to add a quirk based on DMI information, you can use 
pmf_get_platform(9) to fetch this information.

Cheers,
Jared