- 24 Aug, 2004 12 commits
-
-
Dave Jones authored
Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
Some daemons try to set the speed to the same speed we're currently running at. Detect that, and bail out early before we fiddle with registers and such. Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
From: Sven Traenkle The second part adresses a problem of resetting the max cpu-freq when unloading the driver. This didn't work for my cpu and I doubt it does for other. There is no need to pass the computed index of the max. multiplier in the clock_ratio[] table to longhault_table[] cause the longhaul_setstate function works with the clock_ratio[] index. Changing the while loop to a for loop with upper limit isn't actually necessary as long as the driver is bug free, but thats IMHO not yet the case, so I suggest this change in order to not loop endlessly or read beyond the limits of the clock_ratio array. Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
From: Sven Traenkle. here's a patch that solves some issues I have with the longhaul cpufreq driver on my epia 6000CL/Via EDEN (actually reporting as CentaurHauls, family 6, model 7, VIA Samuel 2). The driver tries to compute the fsb speed while it could actually use the fixed values (as it does for model == 6). I got this change from the via forum, so no credits to me. Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
By defining the cpu type at startup, we can make a lot of comparisons a lot more obvious what they are meaning. Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
If its >= 1000MHz print it as GHz. Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
into delerium.codemonkey.org.uk:/mnt/data/src/bk/cpufreq
-
Dave Jones authored
Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
We currently don't do voltage scaling, but we can at least set things up to prepare for when we do. Signed-off-by: Dave Jones <davej@redhat.com>
-
Dave Jones authored
This makes some of the code quite a bit cleaner, and a lot more obvious whats going on on which CPUs. Signed-off-by: Dave Jones <davej@redhat.com>
-
- 23 Aug, 2004 28 commits
-
-
Linus Torvalds authored
-
Paul Mackerras authored
This patch changes hose_list from a simple linked list to a "list.h"-style list. This is in preparation for the runtime addition/removal of PCI Host Bridges. Signed-off-by: John Rose <johnrose@austin.ibm.com> Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Nathan Fontenot authored
On some platforms (notably power5) you can't enable surveillance (firmware/service processor watchdog) from the kernel - you have to do it in the firmware. This patch changes enable_surveillance() to make the message that is printed in this situation more informative. Additionaly, the rtas_call was changed to rtas_set_indicator so as to avoid having to handle RTAS_BUSY returns. Signed-off-by: Nathan Fontenot <nfont@austin.ibm.com> Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
bk://ppc.bkbits.net/for-linus-ppc64Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Linus Torvalds authored
The code doesn't actually _care_ about 32/64-bit issues, only about F_SETLK vs F_SETLKW, and the F_SETLK64 doesn't exist except as a compatibility thing on 64-bit architectures (since the regular one already _is_ 64-bit, of course).
-
http://nfsclient.bkbits.net/linux-2.6Trond Myklebust authored
into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.6
-
Trond Myklebust authored
server are not allowed to be interrupted as that may result in the client and server disagreeing.
-
Trond Myklebust authored
recall ability. Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
NFS4ERR_CB_PATH_DOWN error.
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
into fys.uio.no:/home/linux/bitkeeper/work/nfsclient-2.6
-
http://nfsclient.bkbits.net/linux-2.6Trond Myklebust authored
into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.6
-
Trond Myklebust authored
rather than an inode argument. Fix up nfs_instantiate() and _nfs4_do_open to use this since doing a new lookup might be racy.
-
Trond Myklebust authored
NFS4ERR_DELAY on the GETATTR call.
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
that hangs off filp->private_data. As a side effect, this also cleans up the NFSv4 private file state info. Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
operations by using a per-server read/write semaphore. Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-
Trond Myklebust authored
NFS4ERR_DELAY properly. Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
-