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.

This brings sa1100fb up to date with 2.5.54.

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.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

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).

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 ]

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into groveronline.com:/root/bk/linux-acpi

into home.transmeta.com:/home/torvalds/v2.5/linux

This also cleans up the machine check code generally.

into samba.org:/home/paulus/kernel/for-linus-ppc

into home.transmeta.com:/home/torvalds/v2.5/linux

into home.transmeta.com:/home/torvalds/v2.5/linux

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.

into kernel.bkbits.net:/home/davem/sparc-2.5

into kernel.bkbits.net:/home/davem/net-2.5

- Merged AES code from Adam J. Richter <adam@yggdrasil.com>
- Add kconfig help and test vector code from
  Martin Clausen <martin@ostenfeld.dk>
- Minor cleanups: removed EXPORT_NO_SYMBOLS (not needed for 2.5),
  removed debugging code etc.
- Documentation updates.

into kroah.com:/home/linux/linux/BK/gregkh-2.5

Since we killed off the broken 486 strings copies,
the config item isn't needed any longer.

Next in line for the -W cleanups is this patch from Willy
which I've been carrying since 2.5.29 or so. Should be no
functional differences, just no more warnings when we compile
with -W

s/boundry/boundary/

Without this fix, compiling with CONFIG_DEBUG_SPINLOCK
dies with an unknown variable error..

This looks extremely suspect to me, and seems like
it will prefetch past the end of the pmd, which is a no no.