[lkml]   [2008]   [Jun]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: linux-next: Tree for June 13: IO APIC breakage on HP nx6325
    > Otherwise you throw this burden onto users who
    > (1) don't expect things to stop working,
    > (2) may not be able to figure out themselves what the right workaround is,
    > (3) may not be able to make hardware manufacturers do anything.

    Right thing would be to revert the guilty patches until these
    problems are resolved.

    > If there's a configuration that worked before your patch and doesn't work
    > after it, you're hurting the users of that configuration.

    ... also past experience is that DMI tables don't work well for this.
    We tried that early when ACPI was still very problematic and it turned
    out to be a flawed non-scalable strategy,

    Typically the configurations causing problems are in multiple motherboards
    with different DMI strings and it's very difficult to catch them all.

    Also sometimes BIOS behaviour changes over versions and that's tricky to catch
    with the standard DMI matches.

    One way that would half way scale is to check for specific configurations
    based on PCI-IDs and knowledge of the config space of these chipset,
    although it's also not ideal because often multiple chipset generations
    with different PCI-IDs have similar issues.


     \ /
      Last update: 2008-06-30 02:37    [W:0.019 / U:0.728 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site