# dmidecode 2.9
SMBIOS 2.31 present.
19 structures occupying 915 bytes.
Table at 0x000DC010.
Handle 0x, DMI type 0, 20 bytes
BIOS Information
Vendor: Phoenix Technologies LTD
Version: R0091N0
Release Date: 07/10/2006
Address: 0xE4510
Runtime Size:
From: Alexey Starikovskiy [EMAIL PROTECTED]
Refer to Documentation/power_supply_class.txt for interface description.
Signed-off-by: Alexey Starikovskiy [EMAIL PROTECTED]
---
drivers/acpi/battery.c | 201 +++-
1 files changed, 179 insertions(+), 22
What's the way forward if we have a current BIOS with ACPI but no SMBIOS?
acpi=force works as expected.
Is SMBIOS a requirement with ACPI? If not, what would a patch need to
do to correctly identify a working ACPI without SMBIOS present to
avoid the blacklist?
Thanks,
-- Ken
-
To
Quoting Len Do not give an option to users to shoot themselves in the foot.
Remove the configurability of ladder and menu governors as they are
needed for default policy of cpuidle. That way users will not be able to
have cpuidle without any policy loosing all C-state power savings.
Retain the old policy in processor_idle, so that when CPU_IDLE is not
configured, old C-state policy will still be used. This provides a
clean gradual migration path from old acpi policy to new cpuidle
based policy.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index:
Quoting Len Do not give an option to users to shoot themselves in
the foot.
Odd, I thought that was a Windows attitude, and Unix/Linux was the
opposite.
All the rope and more...
Bob
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Venki Pallipadi
Sent:
Add interface to enable usb-bluetooth device in Toshiba notebook.
Index: linux-2.6.23-rc6/drivers/acpi/toshiba_acpi.c
===
--- /usr/src/linux-2.6.23-rc6.orig/drivers/acpi/toshiba_acpi.c 2007-07-09
01:32:17.0 +0200
+++
On Tuesday 11 September 2007 05:14:56 pm Bjorn Helgaas wrote:
...
So I'm interested in feedback on the following patches, which do not
export sal_lock, but rather export functions that can be used to call
SAL or other native firmware interfaces.
Hi Tony,
I haven't heard much feedback, and I
From: Zhang Rui [EMAIL PROTECTED]
File name should be unique in the same directory.
In order to keep the back-compatibility, only a warning is given
currently, but actions must be taken to fix it when such duplicates
are detected.
Bug report and a simple fix can be found here:
ACPI spec (ver 3.0a, p289) requires IDE power on/off executes ACPI _PSx
methods. As recently most PATA drivers use libata, this patch adds _PSx
method support in libata. ACPI spec doesn't mention if SATA requires the
same _PSx method, but executing _PSx for SATA should be ok I think.
Shaohua Li wrote:
ACPI spec (ver 3.0a, p289) requires IDE power on/off executes ACPI _PSx
methods. As recently most PATA drivers use libata, this patch adds _PSx
method support in libata. ACPI spec doesn't mention if SATA requires the
same _PSx method, but executing _PSx for SATA should be ok I
On Thu, 2007-09-13 at 23:21 -0400, Jeff Garzik wrote:
Shaohua Li wrote:
ACPI spec (ver 3.0a, p289) requires IDE power on/off executes ACPI _PSx
methods. As recently most PATA drivers use libata, this patch adds _PSx
method support in libata. ACPI spec doesn't mention if SATA requires the
Subject: set _DOS to 0 by default
From: Zhang Rui [EMAIL PROTECTED]
Many ACPI machines currently reprogram the active display output
automatically when the user presses the display toggle switch on
the keyboard. However, this behavior violates the ACPI spec,
because the system modifies some
13 matches
Mail list logo