- 12 Sep, 2005 40 commits
-
-
Craig Shelley authored
Three new device IDs for CP2101 USB to UART Bridge Signed-off-by:
Craig Shelley <craig@microtron.org.uk> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Alan Stern authored
This patch (as558) removes from the UHCI driver a kernel timer used for checking Full Speed Bandwidth Reclamation (FSBR). The checking can be done during normal root-hub polling; it doesn't need a separate timer. Signed-off-by:
Alan Stern <stern@rowland.harvard.edu> Signed-off-by:
-
Alan Stern authored
This patch (as549) introduces two small changes in the HCD glue layer. The first simply removes a redundant test. The second allows root-hub polling to continue for a single iteration after a host controller dies; this is needed for the patch that follows. Signed-off-by:
-
Stelian Pop authored
This is a driver for the USB touchpad which can be found on post-February 2005 Apple PowerBooks. This driver is derived from Johannes Berg's appletrackpad driver [1], but it has been improved in some areas: * appletouch is a full kernel driver, no userspace program is necessary * appletouch can be interfaced with the synaptics X11 driver[2], in order to have touchpad acceleration, scrolling, two/three finger tap, etc. This driver has been tested by the readers of the 'debian-powerpc' mailing list for a few weeks now and I believe it is now ready for inclusion into the mainline kernel. Credits go to Johannes Berg for reverse-engineering the touchpad protocol, Frank Arnold for further improvements, and Alex Harper for some additional information about the inner workings of the touchpad sensors. Signed-off-by:Stelian Pop <stelian@popies.net> Signed-off-by:
-
Thomas Winischhofer authored
here is a new and extended version of the sisusbvga (previously: sisusb) driver. The patch is against 2.6.13 and updates the driver to version 0.0.8. Additions include complete VGA/EGA text console support and a build-in display mode infrastructure for userland applications that don't know about the graphics internals. Fixes include some BE/LE issues and a get/put_dev bug in the previous version. Other changes include a change of the module name from "sisusb" to "sisusbvga". The previous one was too generic IMHO. Please note that the patch also affects the Makefile in drivers/video/console as the driver requires the VGA 8x16 font in case the text console part is selected. Heavily tested, as usual. Please apply. One thing though: I already prepared for removal of the "mode" field and the changed "name" field in the usb_class_driver structure. This will perhaps need some refinement depending on whether you/Linus merge the respective core changes before or after 2.6.14. Signed-off-by:
Thomas Winischhofer <thomas@winischhofer.net> Signed-off-by:
-
Greg KH authored
This reverts 22af8878 commit. Signed-off-by:
-
Andi Kleen authored
Signed-off-by:Linus Torvalds <torvalds@osdl.org>
-
Andi Kleen authored
The nodes are not set online yet at this point. Signed-off-by:
Andi Kleen <ak@suse.de> Signed-off-by:
-
Andi Kleen authored
Signed-off-by: -
Andi Kleen authored
Also use for_each_node_mask instead of hand crafted loops. Signed-off-by: -
Chuck Ebbert authored
Original patch from Bertro Simul This is probably still not quite correct, but seems to be the best solution so far. Signed-off-by: -
Jan Beulich authored
As mentioned before, the size of the bug frame can be further reduced while continuing to use instructions to encode the information. Signed-off-by:
Jan Beulich <jbeulich@novell.com> Signed-off-by:
-
Andi Kleen authored
Otherwise it will generate warnings and be generated many times. Signed-off-by:
-
Andi Kleen authored
Allow frame pointer and fix help text. Signed-off-by:
-
Al Viro authored
... and with that all instances in arch/x86_64 are gone. Signed-off-by:
Al Viro <viro@zeniv.linux.org.uk> Signed-off-by:
-
Chuck Ebbert authored
This is the same patch that went into i386 just before 2.6.13 came out. I still can't build 64-bit user apps, so I tested with program (see below) in 32-bit mode on 64-bit kernel: Before: $ fpsig handler: nr = 8, si = 0x0804bc90, vuc = 0x0804bd10 handler: altstack is at 0x0804b000, ebp = 0x0804bc7c handler: si_signo = 8, si_errno = 0, si_code = 0 [unknown] handler: fpu cwd = 0xb40, fpu swd = 0xbaa0 handler: i387 unmasked precision exception, rounded up After: $ fpsig handler: nr = 8, si = 0x0804bc90, vuc = 0x0804bd10 handler: altstack is at 0x0804b000, ebp = 0x0804bc7c handler: si_signo = 8, si_errno = 0, si_code = 6 [inexact result] handler: fpu cwd = 0xb40, fpu swd = 0xbaa0 handler: i387 unmasked precision exception, rounded up Signed-off-by:
Chuck Ebbert <76306.1226@compuserve.com> Signed-off-by:
-
Chuck Ebbert authored
The x86_64 nmi code is missing a newline in one of its messages. I added a space before the CPU id for readability and killed the trailing space on the previous line as well. Signed-off-by:
-
Jan Beulich authored
While only cosmetic for x86-64, this adjusts the cmpxchg code appearantly inherited from i386 to use more generic constraints. Signed-off-by:
-
Jan Beulich authored
Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Jan Beulich authored
Rather than blindly re-enabling interrupts in oops_end(), save their state in oope_begin() and then restore that state. Signed-off-by:
-
Andi Kleen authored
The only difference was the inline assembly, so move that into asm/msr.h and merge with the i386 version. This adds some missing sysfs support code to x86-64. Signed-off-by:
-
Al Viro authored
Signed-off-by:
-
Jan Beulich authored
Being the foundation for reliable stack unwinding, this fixes CFI unwind annotations in many low-level x86_64 routines, plus a config option (available to all architectures, and also present in the previously sent patch adding such annotations to i386 code) to enable them separatly rather than only along with adding full debug information. Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
This avoids races with the APIC broadcast/mask modes. Signed-off-by:
-
Andi Kleen authored
Currently just defined to their non range parts. Pointed out by John Linville Signed-off-by:
-
Andi Kleen authored
- Report PXMs instead of nodes - Report the correct PXM, not always the one of node 1. - Only warn for the case of a PXM overlapping by itself Signed-off-by:
-
Andi Kleen authored
They were previously static. Signed-off-by:
-
Ashok Raj authored
Signed-off-by:
-
Adrian Bunk authored
They should be identical in the kernel now, but this makes it consistent with other code. Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
Andi Kleen authored
Nick points out it never worked because PageReserved was set and it might cause problems later on. Also HOTPLUG_CPU is much more common now so let's care not too much about the !hotplug case. Cc: nickpiggin@yahoo.com.au Signed-off-by:
-
Andi Kleen authored
Noted by Ashok Raj Signed-off-by:
-
Alexander Nyberg authored
Signed-off-by:
-
Nakul Saraiya authored
Needed for some newer Opteron systems with E stepping and memory relocation enabled. The node addresses are different in lower bits now so the nodemap hash function needs to be enlarged. Signed-off-by:
-
Jim Paradis authored
When I gave proposed the fix to pfn_valid() for RHEL4, Stephen Tweedie's sharp eyes caught this: Signed-off-by: -
Andi Kleen authored
As noted by matz@suse.de The problem is, that on i386 the syscallN macro is defined like so: long __res; \ __asm__ volatile ("int $0x80" \ : "=a" (__res) \ : "0" (__NR_##name),"b" ((long)(arg1)),"c" ((long)(arg2)), \ "d" ((long)(arg3)),"S" ((long)(arg4)),"D" ((long)(arg5))); \ If one of the arguments (in the _llseek syscall it's the arg4) is a pointer which the syscall is expected to write to (to the memory pointed to by this ptr), then this side-effect is not captured in the asm. If anyone uses this macro to define it's own version of the syscall (sometimes necessary when not using glibc) and it's inlined, then GCC doesn't know that this asm write to "*dest", when called like so for instance: out = 1; llseek (fd, bla, blubb, &out, trara) use (out); Here nobody tells GCC that "out" actually is written to (just a pointer to it is passed to the asm). Hence GCC might (and in the above bug did) copy-propagate "1" into the second use of "out". The easiest solution would be to add a "memory" clobber to the definition of this syscall macro. As this is a syscall, it shouldn't inhibit too many optimizations. Signed-off-by: -
Andi Kleen authored
- Add KERN_INFO to printks (from i386) - Use longs instead of ints to accumulate pages. - Fix broken indenting. Signed-off-by:
-
Andi Kleen authored
It only offers extremly dubious security advantages and is not worth the overhead in this critical path. Signed-off-by:
-
