- 24 Nov, 2004 8 commits
-
-
Greg Kroah-Hartman authored
Signed-off-by:Greg Kroah-Hartman <greg@kroah.com>
-
Justin Thiessen authored
Here is the revised adm1026 driver port for kernel 2.6.10-rc2. It takes into account Jean Delvare's and Mark Hoffman's comments and recommendations, and provides pretty much the entire feature set of the 2.4.X kernel driver, but in (hopefully) a manner compliant with the standards for the 2.6.X kernel lm_sensors drivers. As discussed in previous messages, control over the pwm output is provided via: pwm[1-3] {0-255} pwm[1-3]_enable {0-2} (off, manual, automatic fan control) Note that there is really only one pwm register and one enable bit. pwm[2-3] and pwm[2-3]_enable are provided for the sake of a chip-indpendent interface, and are simply RW mirrors of pwm1 and pwm1_enable, respectively. Access to the DAC is provided via: analog_out {0-2500} (millivolts) No way is currently provided to turn on DAC-mediated automatic fan control. See my previous email in this thread for the reasons why. Control over automatic fan "on" temperatures are provided by: temp[1-3]_auto_point1_temp {-128000 - 127000} Hardware-determined hysteresis and range values are revealed in: temp[1-3]_auto_point1_temp_hyst {temp[1-3]_auto_point1_temp - 6000} temp[1-3]_auto_point2_temp {temp[1-3]_auto_point1_temp + 20000} Failsafe critical temperatures at which the fans go to maximum speed are controled via: temp[1-3]_crit_enable {0-1} (off, on) temp[1-3]_crit {-128000 - 127000} Again, there is really only one "enable critical-temperature-fan-maximization" bit. temp[2-3]_crit_enable are simply RW mirrors of temp1_crit_enable These values override any values set for the pwm-mediated automatic fan control. VRM is now set via Rudolf Marek's functions. VID is read from the assumed correct set of pins (GPIO11-GPIO15), and no longer a user-writable field. In keeping with Greg KH's changes, normal_i2c_range normal_isa_range have been removed, and normal_i2c has been updated to enumerate all addresses. (Just adding 0x2d) Finally, the val-comparison-before-assignment bug has been corrected. Signed-off-by:Justin Thiessen <jthiessen@penguincomputing.com> Signed-off-by:
-
Aristeu Sergio Rozanski Filho authored
[I2C] i2c-elektor: adding missing casts Signed-off-by:
Aristeu Sergio Rozanski Filho <aris@cathedrallabs.org> Signed-off-by:
-
Aristeu Sergio Rozanski Filho authored
this patch get rid of cli()/sti(). while correcting this I found that when a process wakes by an interrupt, pcf_pending doesn't come back to 0 and next caller will return imediately. also, there are other drivers with the exact same problem. if you don't have any comments on this, I'll do the same for other drivers. [I2C] i2c-elektor: getting rid of cli()/sti() usage Signed-off-by:
-
Evgeniy Polyakov authored
Remove unneded inlines. Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
Evgeniy Polyakov <johnpol@2ka.mipt.ru> Signed-off-by:
-
Evgeniy Polyakov authored
W1_DS9490R_BRIDGE kconfig typo. Signed-off-by:
-
Evgeniy Polyakov authored
Do not panic if netlink socket was not created. This will allow only first device to broadcast it's slave updates. We need kernel connector here. Signed-off-by:
-
Jean Delvare authored
This simple patch increases the verbosity of the w83l785ts hardware monitoring driver. I wrote it months ago in the hope it would help solve a reported problem [1]. Not sure whether it did (no news from user since July), but the extra debug info may help in the future and doesn't hurt otherwise, so let's have this in for every user (not that many AFAIK), just in case. [1] http://bugzilla.kernel.org/show_bug.cgi?id=2899Signed-off-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
-
- 23 Nov, 2004 3 commits
-
-
Jesper Juhl authored
Building with gcc -W revealed this warning: arch/i386/kernel/traps.c: In function `do_general_protection': arch/i386/kernel/traps.c:506: warning: empty body in an if-statement upon inspecting the code I see what looks like a mistakenly placed ";" if (!fixup_exception(regs)) { if (notify_die(DIE_GPF, "general protection fault", regs, error_code, 13, SIGSEGV) == NOTIFY_STOP); return; die("general protection fault", regs, error_code); } That ";" after the second if should go away so the return; before die() is not unconditional. Signed-off-by:Jesper Juhl <juhl-lkml@dif.dk> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Tony Luck authored
Signed-off-by:Tony Luck <tony.luck@intel.com>
-
Tony Luck authored
into intel.com:/data/home/aegl/BK/linux-ia64-release-2.6.10
-
- 22 Nov, 2004 15 commits
-
-
Linus Torvalds authored
Len Brown convinced me that the problem with disabling PCI routing entries wasn't the disable as much as the fact that ELCR needs to be updated when removing the PCI routing. So this reverts the previous cset and updates ELCR as suggested by Len.
-
Bjorn Helgaas authored
Ignore offline CPUs when registering IOSAPIC interrupts. We previously directed interrupts even to offline CPUs, which means that if you have some unused CPUs (e.g., you used "maxcpus="), some interrupts won't work. This really hurts because distro installs typically use "maxcpus=1". Patch by Alex Williamson. Signed-off-by:
Bjorn Helgaas <bjorn.helgaas@hp.com> Signed-off-by:
-
Linus Torvalds authored
This fixes at least some interrupt polarity setup cases. The ACPI guys may want to eventually do this differently, but in the meantime this makes ACPI behaviour closer to non-ACPI behaviour, and fixes known problems. I'll further argue that this protects non-PCI devices that may just share the irq routing from being screwed, but that may or may not be an argument that everybody buys into.
-
Linus Torvalds authored
This depends on the previous ptrace single-step cleanup, and makes sure that signal handling does not lose TF events. This allows debuggers to trace programs that set TF on their own.
-
Linus Torvalds authored
(This makes the naming of "DTRACE" purely historical, since on x86 it now means "single step in progress").
-
Gerd Knorr authored
Update for the tuner module: add support for a new tuner chip. Signed-off-by:
Gerd Knorr <kraxel@bytesex.org> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
Gerd Knorr authored
convert more modules to new-style insmod options. Signed-off-by:
-
Gerd Knorr authored
#ifdef out a currently unused (in-kernel) function, lets see if any out-of-kernel users cry. If not we can drop it altogether later on. Signed-off-by:
-
Gerd Knorr authored
Some places which need adaption to the last video-buf API change where forgotten, this patches fixes them up. Hope I really caught them all now. Signed-off-by:
-
Michael Obster authored
Prevents user-space including spinlock.h which breaks the build. Signed-off-by:
-
Cal Peake authored
Patch below fixes a typo in init/Kconfig for option CC_ALIGN_FUNCTIONS. Signed-off-by:
Cal Peake <cp@absolutedigital.net> Signed-off-by:
-
Russell King authored
The patch below fixes wrong arguments to outw in smc91c92_cs.c Signed-off-by:
Russell King <rmk@arm.linux.org.uk> Signed-off-by:
-
Prasanna Meda authored
Fix the mmput bug introduced while fixing cmdline race. Signed-off-by:
Prasanna Meda <pmeda@akamai.com> Signed-off-by:
-
Tim T. Murphy authored
Here's a patch to include Dell's 4th generation Remote Access Controller ids. Acked-by:
-
Stephen D. Smalley authored
This patch for SELinux fixes a bug in the mapping of socket types to security classes and ensures that Unix seqpacket sockets are mapped to an appropriate security class. The Unix stream security class is re-used in this case as it has the same permission checking applied as for seqpacket. Signed-off-by:
Stephen Smalley <sds@epoch.ncsc.mil> Signed-off-by:
James Morris <jmorris@redhat.com> Signed-off-by:
-
- 21 Nov, 2004 14 commits
-
-
Benjamin Herrenschmidt authored
We just spent some days fighting a rare race in one of the distro's who backported some of timer.c from 2.6 to 2.4 (though they missed a bit). The actual race we found didn't happen in 2.6 _but_ code inspection showed that a similar race is still present in 2.6, explanation below: Code removing a timer from a list (run_timers or del_timer) takes that CPU list lock, does list_del, then timer->base = NULL. It is mandatory that this timer->base = NULL is visible to other CPUs only after the list_del() is complete. If not, then mod timer could see it NULL, thus take it's own CPU list lock and not the one for the CPU the timer was beeing removed from the list, and thus the list_add in mod_timer() could race with the list_del() from run_timers() or del_timer(). Our race happened with run_timers(), which _DOES_ contain a proper smp_wmb() in the right spot in 2.6, but didn't in the "backport" we were fighting with. However, del_timer() doesn't have such a barrier, and thus is subject to this race in 2.6 as well. This patch fixes it. Signed-off-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Benjamin Herrenschmidt authored
The "udbg" code used on ppc64 for early consoles including early serial console recently got a new "default speed" option. This was implemented as a switch case that missed a few important cases, one beeing necessary for a board beeing released soon. This patch fixes it by using the proper division to calculate the dll value for the uart instead of that bogus switch/case. Signed-off-by:
-
Benjamin Herrenschmidt authored
The pci_bus_to_host() inline function used on ppc64 to find the pci_contoller structure a give pci_bus resides on used to contain bogus tree walking code, which fortunately ended up never beeing necessary since "sysdata" always points to a device_node structure that has the proper "phb" field (even if it is not the device-node of the actual P2P, which happens during boot). Signed-off-by:
-
Benjamin Herrenschmidt authored
This patch fixes a typo in the code that parse Open Firmware properties for devices under an "isa" node, the incorrect struct size was used when parsing the "reg" property of these. Signed-off-by:
-
Benjamin Herrenschmidt authored
The ppc64 kernel can be built with a default command line (CONFIG_CMDLINE) for cases where none is provided by the firmware. However, some OF implementation always pass a "bootargs" property that only contains the "0" terminating byte of a C string which caused us to think there was a command line, and not use the built-in one. This patch fixes it. Signed-off-by:
-
Antonino Daplas authored
third argument in module_param is the sysfs permission not a default value. This fixes things for rivafb in 2.6.10-rc2: Signed-Off-By:
Guido Guenther <agx@sigxcpu.org> Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Antonino Daplas authored
From Guido Guenther <agx@sigxcpu.org> this patch against 2.6.10-rc2 finally detects rivafb on NV30 based power books by adding the pciid. Wolfram Quester tested it and reported it working. It also cleans up the error code reported from the probe function. From Antonino Daplas <adaplas@pol.net> - do not validate mode if monitor specifications are not available Signed-Off-By:
-
Antonino Daplas authored
- Do a set_par very late instead of during fbcon_blank by setting the FBINFO_MISC_MODESWITCHLATE flag which should help prevent lockups when switching from X - Shorten chipset names that were missed before - Do not validate modeline if monitor specifications are not available Signed-off-by:
-
Antonino Daplas authored
This patch fixes the screen corruption resulting from neofb cleanup. Signed-off-by:
-
Alexander Viro authored
ChangeSet "adaplas: [PATCH] fbdev: Add __iomem annotations to hgafb" had actually broken it - it not only added a (useless) cast in rowaddr(), it had also added a dereferencing. Since it is video memory and since we do memory transfers on the resulting "address"... IOW, it's even exploitable - not that there had been a lot of HGA boxen out there, but... This restores the intended behaviour. Signed-off-by:
Al Viro <viro@parcelfarce.linux.theplanet.co.uk> Signed-off-by:
-
Alexander Viro authored
missing __user annotations + removal of gratitious casts in LHS of assignments. Signed-off-by:
-
Alexander Viro authored
Signed-off-by:
-
Alexander Viro authored
Signed-off-by:
-
Alexander Viro authored
Signed-off-by:
-
