- 28 Jan, 2004 5 commits
-
-
Len Brown authored
into intel.com:/home/lenb/src/linux-acpi-test-2.6.2
-
Len Brown authored
into intel.com:/home/lenb/src/linux-acpi-test-2.6.1
-
Dominik Brodowski authored
updates the _PPC handling. It is handled as a CPUfreq policy notifier which adjusts the maximum CPU speed according to the current platform limit.
-
Dominik Brodowski authored
from Dominik Brodowski The acpi cpufreq driver includes a test at startup which detects whether ACPI P-States are supported on any CPU, and whether transitions work. However, this test is faulty: it is only run _after_ the acpi driver is registered, causing race situations. Also, it doesn't save anything _as_ the driver is already registered. So, it can safely be removed.
-
Dominik Brodowski authored
from Dominik Brodowski The current algorithm used by Linux ACPI for passive thermal management has two shortcomings: - if increasing the CPU processing power as a thermal situation goes away, throttling states are decreased later than performance states. This is not wise -- it should be the opposite ordering of going "up". - only if the ACPI CPUfreq driver is used, performance states are used. A generalized approach would offer passive cooling even if the ACPI P-States cpufreq driver cannot be used (faulty BIOS, FixedHW access, etc.)
-
- 27 Jan, 2004 5 commits
-
-
Len Brown authored
into intel.com:/home/lenb/src/linux-acpi-test-2.6.2
-
Len Brown authored
into intel.com:/home/lenb/src/linux-acpi-test-2.6.1
-
Jes Sorensen authored
from Jes Sorensen
-
Len Brown authored
-
Len Brown authored
into intel.com:/home/lenb/src/linux-acpi-test-2.6.2
-
- 26 Jan, 2004 23 commits
-
-
Len Brown authored
into intel.com:/home/lenb/src/linux-acpi-test-2.6.2
-
http://linux-acpi.bkbits.net/linux-acpi-release-2.6.2Linus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
Len Brown authored
into intel.com:/home/lenb/src/linux-acpi-test-2.6.2
-
Len Brown authored
into intel.com:/home/lenb/src/linux-acpi-test-2.6.1
-
Len Brown authored
from ia64 via Alex Williamson
-
Len Brown authored
from Jes Sorensen
-
Len Brown authored
from Jes Sorensen
-
Len Brown authored
-
http://lia64.bkbits.net/to-linus-2.5Linus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
-
Stéphane Eranian authored
-
Grant Grundler authored
-
Andreas Schwab authored
This fixes a conflicting declaration in xbow.c.
-
Matthew Chapman authored
works without trashing any registers.
-
James Simmons authored
This updates the framebuffer docs to reflect the requirement that all driver names must end in fb.
-
James Simmons authored
[FBCON] Fixed the order of which driver is used for the console. Before the api change the last driver loaded became the default one. Now this is not the case.
-
bk://kernel.bkbits.net/davem/irda-2.6Linus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
David S. Miller authored
-
Andrew Morton authored
From: Sam Ravnborg <sam@ravnborg.org> cscope expect to find the list of files used for the database in a file named cscope.files. Generate this file as part of 'make cscope'. This solves http://bugme.osdl.org/show_bug.cgi?id=1948.
-
Andrew Morton authored
The spinlock debugging feature is supposed to work even on uniprocessor kernels. So we need to instantiate kernel_flag regardless of CONFIG_SMP.
-
David S. Miller authored
-
David Mosberger authored
into tiger.hpl.hp.com:/data1/bk/lia64/to-linus-2.5
-
Andi Kleen authored
The LSM changes broke the error checking for queue lengths in IPC_SET. The LSM check would set set err to 0, but the next check expected it to still be -EPERM. Result was that no error was reported, but the new parameters weren't correctly set.
-
- 25 Jan, 2004 3 commits
-
-
Linus Torvalds authored
-
-
Ben Collins authored
-
- 24 Jan, 2004 4 commits
-
-
bk://gkernel.bkbits.net/misc-2.5Linus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
bk://bk.arm.linux.org.uk/linux-2.6-serialLinus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
Russell King authored
-
Russell King authored
tty->driver_data or state->port may end up being NULL in uart_close. Make sure that we correctly clean up in this case, rather than oopsing.
-