Provide LDM-based driver registration/removal interface for drivers
to use.  We make the old device discovery code ignore devices
claimed via the LDM framework.  However, the LDM framework ignores
devices that may be in use by the old device discovery code.  This
is fine since the only devices that will still use the old discovery
code will be SCSI drivers.

Currently, we don't provide a useful dev.name entry.

This updates the Integrator cpufreq code to use the new interfaces,
and makes the sa1100 cpufreq round up the requested frequency.

The second serial port is never present in these machines, so its
pointless listing it in the first place.

- ide_register_hw takes two arguments, not one.
- ide_fix_driveid is no longer used.

This adds ARM support for in_atomic() and asm/numnodes.h

This updates these neponset and sa1111 support to use the new system
device infrastructure in the Linux device model.

Sanitise includes of asm/tlbflush.h, asm/cacheflush.h, asm/proc-fns.h
Implement ARM-specific TLB "shootdown" code.  It turns out that it
is overall more efficient to unconditionally invalidate the whole
TLB rather than entry by entry when removing areas.

This cset fixes the RiscPC decompressor code for the PIC changes.

We use a pointer to a structure rather than a structure to access
params.  With a PIC decompressor, the address of the structure gets
PIC-ified which is not what we want.

Update pcibios_enable_device to only enable requested resources,
mainly for IDE.  Supply a pci_mmap_page_range() function to allow
user space to mmap PCI regions.

This updates the ARM time keeping functions to use tick_nsec/1000
instead of tick.

To keep the Config.in files relatively clean, we use the
following construct:

 if [ "$CONFIG_ARM" = "y" ]; then
    dep_tristate 'Foo' CONFIG_FOO $CONFIG_BAR
 fi

where CONFIG_BAR is some machine implementation or high-level
chip support configuration option.  If CONFIG_BAR is left
empty, then the tristate is offered to the user, which isn't
what we want.  Defining CONFIG_BAR to 'n' prevents the option
being offered.

This is a rule I generally try to implement within
arch/arm/config.in.

This cset makes CONFIG_SA1111 and CONFIG_ARM_THUMB behave that
way.

Since the decompressor supports PIC, even for CONFIG_ZBOOT_ROM,
we can easily allow an image which has been linked to run at
a particular address in ROM to be moved to RAM.  We just need
to make sure that we don't relocate the GOT entries for the
BSS segment.

This cset also implements sa1100-based debugging for the
decompressor.

These two variables are used by more than just the linker;
they're also used by head.S to know where it can safely
place the page tables.  We therefore need to export it
from the Makefile.

These are also highly machine dependent; we don't want
to duplicate the same set of conditionals for cpp and
for the makefiles.

arch/arm/Makefile also contained a stray close-paren.  I'm
submitting this one to the lost property office.

We also always pass -mno-fpu to the assember; this
guarantees that any floating point will be caught.

SPARC was unconditionally setting CONFIG_SERIAL_CORE_CONSOLE to y
and conditionally setting CONFIG_SERIAL_CORE depending on the Sparc
sub-drivers.  In addition, the core serial driver for SPARC is
always built, so we end up with link errors.

We instead make CONFIG_SERIAL_CORE{,_CONSOLE} dependent on building
the SPARC core driver (CONFIG_SERIAL_SUNCORE).

uses fields that do not exist otherwise.

Due to some bugs in byteorder/generic.h linux would always use C handcoded
swab64 for 64bit ntohq or cpu_to_be64.  The C version is very inefficient
and expands to 30+ instructions of horrible code.

This hurts on filesystems that use on disk big endian data structures
with 64bit data types.

This patch adds an assembly optimized swab64 to fix it. Now bswab64 is
4 instructions when your CPU supports bswap and 9 when it doesn't.
Tests were done with gcc 3.2, may be different on older gcc.

This is good for ~600 bytes code size reduction in XFS (gcc 3.2):
Before:
 503199    3296    1682  508177   7c111 fs/xfs/xfs.o
After:
 502543    3296    1682  507521   7be81 fs/xfs/xfs.o

Also should be faster.

Also some minor cleanups in the file.

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

Most of these changes have been tested and used in the 2.4 tree, so this
is mostly a forward port of 2.4 bugfixes.

* C99 initializers
* Added specific initializations instead of assuming that the private
  part of the inode is already initialized.
* Remove unused code.
* Moved container file to the struct file private data, this is to
* correct the session semantics model when file updates are fetched from
* the server (old 'sessions' shouldn't see the new container yet).
* Fixed consistency (and occasional oopes) when mmap-ing Coda files.
* Fixing up inode numbers in readdir, old libc5 getcwd was broken.
* Nuked upcall_stats, all of this can easily be maintained in userspace,
  and the existing code suffers from overflows in the fixed point
  calculations.

- Fix some printk warnings in 3c59x.c (inl() now returns a long).

- ext3 warning fix from Stephen Hemminger: "__FUNCTION__ is a
  constant and gcc warns about passing it as a mutuable string."

- Fix a return-with-BKL-held in isofs_readdir()

- paride 64-bit sector_t fix (Bill Irwin)

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

This syncs up the cyclone-timer code w/ Greg's changes from this
morning.

In the current kernels, when a PCMCIA card is inserted into or
removed from a socket, the kernel oopses because yenta_bh() tries to
dereference a NULL pointer.

The attached patch initialises the argument to yenta_bh() so that this
doesn't happen.

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

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

Add _request and _parse methods for nfsd.fh and
nfsd.exports tables.

nfsd.fh maps a filehandle-fragment to a path for a client,
and nfsd.exports maps a path to export options for a client.

a message should be:
   nfsd 10.0.1.1 {Expirydate}  domainname

if domainname is empty, then this is a NEGATIVE entry: that
IP address will be deined access.

{Expirydate} is seconds since unix epoch.
e.g.  1036105199 for midnight, halloween.

get_word understands both \x and \012 quoting styles.

This is the first upcall to actually be coded.
A request will look like:
   nfsd 127.0.0.1

This code enhances 'cache_check' to try to initiate
an up-call if the cache entry is not up-to-date, and also
defines add_word and add_hex for formating up-call
requests.  See rpc-cache.txt for more detail.

[PATCH] kNFSd: Create files: /proc/net/rpc/$CACHENAME/channel for communicating cache updates with kernel

Each cache gets it's own 'channel' at
  /proc/net/rpc/$CACHENAME/channel

Reads from the file will return all pending requests, one at a time.
select will block when at end of file.
writes will pass full lines in to be processed.

cache.c gets code to allow a 'request' to be referred pending
an update of a cache item, and revisited when the item is
updates.

svcsock.c gets code to store the relevant part of a request on deferral, and
to re-queue it when the cache item that caused the deferral is
filled in.

Rather than possibly modifying a request (as
xdr_decode_string can) we use xdr_decode_string_inplace
to symlink contents.  This string may not be nul terminated
(though it often is) so in the 'unlikely' event that is isn't
nul terminated, we copy it into a kmalloced space first.

It might be nice if vfs_symlink took a length, but then every
filesystem would have to as well....

We are going to want rpc request to be immutable so that
we can take a copy and put it aside to be processed later.
Currently the tcp code writes the response into the same
buffer as the request, thus corrupting the request.
With this patch, the response goes after the request.  There should
always be enough room as large reqeusts (Write) has small
responses, and large responses (read) are for small requests.

buflen is changed for requests to record the length of the
request.  It already gets reset for each new request.

This introduces two caches, svc_export_cache (nfsd.exports) and
svc_expkey_cache (nfsd.fh).
nfsd.exports maps client+directory  ->  export options.
nfsd.fh maps client + filehandle-fragment -> directory.

A major part of this change is that export entries are now reference counted,
so we have to be careful  to keep those counts correct.