Bug 1307 - Need whitelist for date-based ACPI-disable
Summary: Need whitelist for date-based ACPI-disable
Status: CLOSED WILL_FIX_LATER
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Len Brown
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-01 18:23 UTC by Andy Grover
Modified: 2004-03-05 11:42 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.4.23-pre6
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Andy Grover 2003-10-01 18:23:16 UTC 
My T20 works great with Linux ACPI enabled. However, even BIOS updates from 
2003 leave the DMI BIOS date as December 1999. Therefore, I need to add 
acpi=force to use ACPI.

This would be a perfect candidate for adding to a whitelist to override the 
DMI date exclusion -- once the infrastructure for the whitelist was added, 
that is. I looked at dmi_scan.c but wasn't sure the cleanest way to do this. 
Thoughts?
Comment 1 Len Brown 2003-11-12 22:07:08 UTC 
My thought is to get IBM to fix the BIOS. 
If they didn't do DMI, we wouldn't disable ACPI. 
But they do it and do it wrong... (can you attach dmidecode BTW) 
 
If there is a big outcry for over-riding the cutoff date automatically, 
then lets add a whitelist.  But if there is not, then lets 
keep it simple by not doing it -- b/c acpi=force is available.
Comment 2 Len Brown 2004-03-05 11:42:51 UTC 
DEFERRED comes up as OPEN in my list.
lets close this bug, I haven't seen a stampede of reqeusts.
If it comes up again we can always re-open.

-Len
Note You need to log in before you can comment on or make changes to this bug.