Patch from Guennadi Liakhovetski

The enclosed patch includes support for the trizeps board, based on the
StrongARM-1110 CPU, machine number 74. The patch is built against
2.5.44-rmk1. Only the core files - from arch/arm and
include/asm-arm directories.

Patch from Guennadi Liakhovetski

A minor update, trizeps.h has to be included explicitely now, since
platform-specific headers are commented out in hardware.h

Patch from Guennadi Liakhovetski

The enclosed patch includes trizeps-specific IDE code. It adds a
Trizeps-specific section to asm/arch/ide.h. The patch is built
against 2.5.44-rmk1.

Patch from Stefan Eletzhofer

This patch adds basic support for the HackKit Core CPU Board.

Patch from Dirk Behme

Patch some typos in uart00.c. frame is selected with FE_MSK and for OE_MSK rds
must be used.

We now really run the ebsa110 kernel timer at 200Hz, and convert
where necessary to 100Hz for user space.

- Add scsi devclass support.
- Convert to use ioremap and friends.
- Fix oops which can occur when driver claims interrupt, and there's
  an interrupt pending - move to a two-level fas driver initialisation.

Add {read,write}[bwl] functionality to Acorn RISC PC.  Add
{read,write}s[bwl] functionality for all.

These two macros got missed when converting from the task-struct on
stack to thread_info-struct on stack.

Since CPUFreq now uses the driver model, we need to register a CPU
device with the driver model.

Some linkers obey the linker script and make .stack unallocatable,
others obey the flags from the object files.  Dropping "a" should
make the end result deterministic in all cases.

print_symbol() becomes a NOP when CONFIG_KALLSYMS=n, so we loose
the new line character as well.  Explicitly call printk("\n").

Ensure SCpnt->request_bufflen is initialised correctly when we
request sense information.

100 characters is too small for the SCSI "info" string buffer; the
last few characters appear to get stomped on.  Make the buffer 150
characters long.

printk was missing a new line, and displaying the (fixed) IRQ number
is rather meaningless.

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

__virt_to_bus/__bus_to_virt depended on INTEGRATOR_HDR0_SDRAM_BASE
Unfortunately, this is defined in arch-integrator/platform.h, and
we really don't want to include it in memory.h.

We instead use BUS_OFFSET, which will eventually depend on the CPU
number in the system.

Only default BLK_DEV_IDEDMA on BLK_DEV_IDEDMA_ICS if ARCH_ACORN is
set, not if ARM is set.  There are PCI ARM systems out there!

Ensure that we clean up properly after initialisation error,
releasing all claimed resources in an orderly manner and
returning the correct error code.

Add cfbfillrect / cfbcopyarea / cfbimgblt objects for SA1100fb.
Remove redundant "pm" member.

Found a buglet in the marvel code -- doesn't change the number of IRQS
just the logic to get there.. This applies on top of the other marvel
code.

/jeff

into kanga.twiddle.net:/home/rth/linux/axp-2.5

to header files where they belong.

of AGP and SRMCONS patches.

From Jeff.Wiedemeier@hp.com.

(Titan / Marvel), Kconfig and headers.

From Jeff Wiedemeier.

Patch from Erich Focht

This adds a hook to rebalance globally across nodes every NODE_BALANCE_RATE
iterations of the rebalancer. This allows us to easily tune on an architecture
specific basis how often we wish to rebalance - machines with higher NUMA
ratios (more expensive off-node access) will want to do this less often.
It's currently set to 100 for NUMA-Q and 10 for other machines. If the
imbalance between nodes is > 125%, we'll rebalance them. The hook for this
is added to the NUMA definition of cpus_to_balance, so again, no impact
on non-NUMA machines.

Patch from Michael Hohnbaum

This adds a hook, sched_balance_exec(), to the exec code, to make it
place the exec'ed task on the least loaded queue. We have less state
to move at exec time than fork time, so this is the cheapest point
to cross-node migrate. Experience in Dynix/PTX and testing on Linux
has confirmed that this is the cheapest time to move tasks between nodes.

It also macro-wraps changes to nr_running, to allow us to keep track of
per-node nr_running as well. Again, no impact on non-NUMA machines.