These are some minor patches I already posted...
All are patched against 2.6.18-rc2.
Do only load asus acpi module when model is listed
Description: There are machines that have a device with HID: ATK0100
(Asus) and a device with HID SNY5001 (Sony). Bad things happen if sony
and asus driver are
Exit ACPI processor module gracefully if acpi is disabled
Description: processor module might oops when machine is booted without
acpi support and the module gets rmmodded.
Module must still be loadable to provide cpufreq functionality even
without acpi.
Reference -
Hello.
This patch is to avoid returning negative value for node id if _PXM is not
defined in ACPI's DSDT. There are 2 possible cases.
1) The hot-add code is executed with NUMA kernel on NON-NUMA box.
2) Firmware expects only SRAT table's information to find pxm,
and it doesn't expect
Fix an obviously broken kfree() in acpi/i2c_ec device initialization
error path.
Signed-off-by: Jean Delvare [EMAIL PROTECTED]
---
This function would benefit from some improvements (single error path,
kzalloc) but let's fix that obvious bug first. This would preferably go
to Linus before 2.6.18.
On Tue, 2006-08-01 at 17:58 +0400, Alexey Starikovskiy wrote:
Thomas,
Is it possible to use DMI interface for this kind of system identification?
IMO it should be sufficient to use the already provided Asus hotkey
model identification.
Using dmidecode to check for Asus and then fallback to the
On Tue, 2006-08-01 at 20:11 +0400, Alexey Starikovskiy wrote:
Checks for Samsung P30/P35 are real hacks IMHO.
Why?
Thomas
Thomas Renninger wrote:
On Tue, 2006-08-01 at 17:58 +0400, Alexey Starikovskiy wrote:
Thomas,
Is it possible to use DMI interface for this kind of system
On Tue, 2006-08-01 at 22:34 +0900, Yasunori Goto wrote:
Hello.
This patch is to avoid returning negative value for node id if _PXM is not
defined in ACPI's DSDT. There are 2 possible cases.
1) The hot-add code is executed with NUMA kernel on NON-NUMA box.
2) Firmware expects only
