These calls no longer take "level" arguments, so there's no need to
call them multiple times.

Since we're now 32-bit "armv" only, we don't need to select the
linker script in vmlinux.lds.S.  Also, whoever moved vmlinux.lds.S
into arch/arm/kernel forgot to move the other scripts.

This cset replaces arch/arm/kernel/vmlinux.lds.S with
arch/arm/vmlinux-armv.lds.in, and deletes the obsolete scripts.

Patch from Nicolas Pitre

In both 2.5.70-rmk1 and 2.4.19-rmk7 the syscall macros are clobering
the returned error value when building library code.

Example code:

#include <linux/unistd.h>
#include <errno.h>
extern int fake_syscall(int x, int y, int z);
_syscall3(int, fake_syscall, int, x, int, y, int, z)

Current generated code:

fake_syscall:
        @ args = 0, pretend = 0, frame = 0
        @ frame_needed = 0, uses_anonymous_args = 0
        str     lr, [sp, #-4]!
        swi     __NR_fake_syscall
        cmn     r0, #126
        ldrls   pc, [sp], #4
        bl      __errno_location
        rsb     r3, r0, #0
        str     r3, [r0, #0]
        mvn     r0, #0
        ldr     pc, [sp], #4

In the code above, whenever the return value is an error code, it
is lost due to the call to __errno_location. And because of the
asm("r0") constraint on the variable __res the compiler continues
using r0 for it even if it's now a pointer value.  errno ends up with
a totally bogus value.

With the patch below the above code becomes:

fake_syscall:
        @ args = 0, pretend = 0, frame = 0
        @ frame_needed = 0, uses_anonymous_args = 0
        stmfd   sp!, {r4, lr}
        swi     __NR_fake_syscall
        cmn     r0, #126
        mov     r4, r0
        bls     .L3
        bl      __errno_location
        rsb     r3, r4, #0
        str     r3, [r0, #0]
        mvn     r4, #0
.L3:
        mov     r0, r4
        ldmfd   sp!, {r4, pc}

which is correct.

Oh and added a small estetic change for generated code too.

Patch from Frank Becker

GPIO for 48 MHz clock output is 7 not 8.

Patch from Deepak Saxena

This is an update to patch 1529/1 that cleans up the code so we don't need 
#ifdef's for little vs. big-endian systems. Tested on both systems with
various network apps (ping, ftp, tftp, ssh, telnet, NFS root, http) with no
issues.

Patch from Deepak Saxena

Patch from Deepak Saxena

Patch from Deepak Saxena

Removes extraneous bits that belong to separate IOP3xx PCI cleanup patch
Supersedes 1618/1

Patch from Deepak Saxena

Patch from Deepak Saxena

Small cleanups for ADIFCC and IOP3XX machine types to support
ATAG parameters. Working with Intel and ADI to get updated 
bootloaders that pass the tags. 

Also, all known IOP3xx boards have memory starting at 0xa0000000,
so we can remove the redundant ARCH_IQ* zreladdr values.

Patch from Deepak Saxena

Fix IOP321 and IQ80310 timer interrupts to return IRQ_HANDLED

Patch from Deepak Saxena

This is required for usr/initramfs_data.o to build properly when
CONFIG_CPU_BIG_ENDIAN is enabled.

Patch from Holger Freyther

Patch from Holger Freyther

Patch from Holger Freyther

see content

into flint.arm.linux.org.uk:/usr/src/linux-bk-2.5/linux-2.5-rmk

This change seems to have been missed for some time.  Remove
__dump_stack(), and convert show_trace_task() to show_stack().

ARM had CONFIG_DEBUG_INFO for ages.  Unfortunately, the new
CONFIG_DEBUG_INFO was rather blindly applied across all architectures.
This removes the duplication from the ARM architecture.

into home.osdl.org:/home/torvalds/v2.5/linux

1) Add another card to the PCMCIA card database.
2) Fix a bug in wireless extensions.
3) Remove extra code for compilation without the firmware loader
4) force-enable CRC32 and FW_LOADER in Kconfig.

It wants big endian vlan tags.  IEEE, or just weird?

into home.osdl.org:/home/torvalds/v2.5/linux

on NCAPINTS value found in include/asm-i386/cpufeature.h.

into redhat.com:/garz/repo/misc-2.6

From: William Lee Irwin III <wli@holomorphy.com>

Contributions from:
	Jan Dittmer <jdittmer@sfhq.hn.org>
	Arnd Bergmann <arnd@arndb.de>
	"Bryan O'Sullivan" <bos@serpentine.com>
	"David S. Miller" <davem@redhat.com>
	Badari Pulavarty <pbadari@us.ibm.com>
	"Martin J. Bligh" <mbligh@aracnet.com>
	Zwane Mwaikambo <zwane@linuxpower.ca>

It has ben tested on x86, sparc64, x86_64, ia64 (I think), ppc and ppc64.

cpumask_t enables systems with NR_CPUS > BITS_PER_LONG to utilize all their
cpus by creating an abstract data type dedicated to representing cpu
bitmasks, similar to fd sets from userspace, and sweeping the appropriate
code to update callers to the access API.  The fd set-like structure is
according to Linus' own suggestion; the macro calling convention to ambiguate
representations with minimal code impact is my own invention.

Specifically, a new set of inline functions for manipulating arbitrary-width
bitmaps is introduced with a relatively simple implementation, in tandem with
a new data type representing bitmaps of width NR_CPUS, cpumask_t, whose
accessor functions are defined in terms of the bitmap manipulation inlines.
This bitmap ADT found an additional use in i386 arch code handling sparse
physical APIC ID's, which was convenient to use in this case as the
accounting structure was required to be wider to accommodate the physids
consumed by larger numbers of cpus.

For the sake of simplicity and low code impact, these cpu bitmasks are passed
primarily by value; however, an additional set of accessors along with an
auxiliary data type with const call-by-reference semantics is provided to
address performance concerns raised in connection with very large systems,
such as SGI's larger models, where copying and call-by-value overhead would
be prohibitive.  Few (if any) users of the call-by-reference API are
immediately introduced.

Also, in order to avoid calling convention overhead on architectures where
structures are required to be passed by value, NR_CPUS <= BITS_PER_LONG is
special-cased so that cpumask_t falls back to an unsigned long and the
accessors perform the usual bit twiddling on unsigned longs as opposed to
arrays thereof.  Audits were done with the structure overhead in-place,
restoring this special-casing only afterward so as to ensure a more complete
API conversion while undergoing the majority of its end-user exposure in -mm.
 More -mm's were shipped after its restoration to be sure that was tested,
too.

The immediate users of this functionality are Sun sparc64 systems, SGI mips64
and ia64 systems, and IBM ia32, ppc64, and s390 systems.  Of these, only the
ppc64 machines needing the functionality have yet to be released; all others
have had systems requiring it for full functionality for at least 6 months,
and in some cases, since the initial Linux port to the affected architecture.

Kernul proggrammers cant spel.