- 12 Jan, 2003 11 commits
-
-
Russell King authored
-
Russell King authored
-
Russell King authored
set_irq_type is redundant for many SA1111 drivers. The active edge is setup by the core SA1111 code for the common case. SA1111 driver names are lower case. Make the sa1111 ohci driver reflect this.
-
Russell King authored
-
Russell King authored
-
Russell King authored
Add sa1100_wdt watchdog support.
-
Russell King authored
-
Russell King authored
Remove the pci_dma functionality from the Acorn SCSI drivers, and replace with the new DMA API, passing in the generic struct device.
-
Russell King authored
Add 00-INDEX and booting documentation, remove obsolete DMA documentation.
-
Russell King authored
-
Russell King authored
-
- 11 Jan, 2003 1 commit
-
-
Russell King authored
cpu-sa11x0: CPUFREQ_ALL_CPUS shouldn't be passed as argument to cpufreq_notify_transition() any more, but the exact CPU number. mach-integrator: cpufreq_notify_transition() isn't called -- which means that the transition notifiers are not informed. This patch adds these callbacks. Also, CPUFREQ_ALL_CPUS can't passed to cpufreq_driver->set_policy any longer, so some code can safely be removed.
-
- 10 Jan, 2003 4 commits
-
-
Russell King authored
This fixes the ARM __put_user implementation. The gcc folk have agreed that the %Qn and %Rn register notation in asm() statements should become official, and have been in all compilers which can be used to build the ARM kernel. In addition, we remove some historical gunk from when put_user() and get_user() was inlined on ARM.
-
Russell King authored
The old consistent memory allocator, which sat behind dma_coherent_alloc() and pci_consistent_alloc() was completely unable to handle allocations from interrupt context because we traditionally used ioremap, which in turn: - allocates memory using GFP_KERNEL for the vm_struct and the page tables themselves. - calls get_vm_area, which uses write_lock, and therefore is unsafe to call from interrupt context. In order to address this issue, a new consistent_alloc() which avoids the above issues has been implemented. Essentially, we set aside a section of the kernel VM space, and pre-allocate page tables to cover this area. We allocate "consistent" memory within this region. The handling of the allocation is designed to be generic; it should be possible to replace the vmalloc(), ioremap() and module_alloc() without too much hastle, but that would clearly be a 2.7 thing at this stage.
-
Russell King authored
This brings sa1100fb up to date with 2.5.54.
-
Russell King authored
The CPU ID no longer contains sufficient information to reliably determine the manufacturer of a specific part. To prevent #ifdef madness appearing in the per-CPU support files, it is better to remove the CPU manufacturer string entirely.
-
- 09 Jan, 2003 17 commits
-
-
http://linux-acpi.bkbits.net/linux-acpiLinus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Andy Grover authored
-
Linus Torvalds authored
-
bk://bk.arm.linux.org.ukLinus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Russell King authored
-
Luca Barbieri authored
This patch, which depends on the previous %ebx -> %ebp patch, removes all pop instruction in the sysenter return path. This leaks the thread_info address to user mode but this shouldn't be a security problem. This is what happens to the various registers: %eax: return value from system call: already in place %ebx, %esi, %edi: saved by the C compiler %ecx, %edx, %ebp: restored by user mode, fixed values by kernels %esp, eip: copied to %ecx/%edx and restored by sysexit %ds, %es: initialized to __USER_DS on kernel entry %cs, %ss: restored by sysexit based on msr %fs, %gs: not modified by the kernel (saved around context switch) eflags: not preserved, iopl saved around context switch FP, XMM: any code that modifies them must save/restore them Note that while it is possible to change %ebx, %esi, %edi, %ecx, %edx or %ebp via struct pt_regs, anything that does should set TIF_IRET or another work flag (and it hopefully already does).
-
Luca Barbieri authored
This patch changes assembly code that accesses thread_info to use %ebp rather than %ebx. This allows me to take advantage of the fact that %ebp is restored by user mode in the sysenter register pop removal patch. vm86() direct return code updated to match [ Linus ]
-
bk://bk.arm.linux.org.ukLinus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
bk://linuxusb.bkbits.net/linus-2.5Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Andy Grover authored
into groveronline.com:/root/bk/linux-acpi
-
Greg Kroah-Hartman authored
-
bk://ppc.bkbits.net/for-linus-ppcLinus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Paul Mackerras authored
This also cleans up the machine check code generally.
-
Paul Mackerras authored
-
bk://68.0.152.218/linux-2.5-miscPaul Mackerras authored
into samba.org:/home/paulus/kernel/for-linus-ppc
-
bk://kernel.bkbits.net/davem/sparc-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
bk://kernel.bkbits.net/davem/net-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
- 08 Jan, 2003 7 commits
-
-
Russell King authored
Supply the old termios, along with the max and min acceptable baud rate to uart_get_baud_rate(). uart_get_baud_rate() will now try to find a baud rate that satisfies the max and min constraint out of (requested rate, old rate, 9600 baud). We remove the code which performed a similar act in uart_get_divisor() and pass an appropriate min and max baud rate to uart_get_baud_rate() based on the UART clock rate.
-
Russell King authored
-
David S. Miller authored
into kernel.bkbits.net:/home/davem/sparc-2.5
-
David S. Miller authored
into kernel.bkbits.net:/home/davem/net-2.5
-
David S. Miller authored
-
David S. Miller authored
-
Oskar Andreasson authored
-