Various quirks from 2.4 and other sources.

Another 2.4 forward port, original from Andrew Morton.

These files use completion, but don't include header.

Another small change from 2.4

Add support for AMD Elan.
(More ELAN patches to follow which rely on CONFIG_MELAN)

Another forward port from 2.4

Self explanatory driver update from vendor.

Support for an extra interrupt router.

introduction of ALSA moved some files around.
This updates various references.

EFI GUID partition table support from Matt Domsch

Clean up capability handling in AGPGart.
This came forward from 2.4

Here's a very tiny bugfix for arch/i386/kernel/mpparse.c in the
2.4.19-pre2 kernel.  It fixes the problem if there is an error in the
MP_processor_info() function where the mpc_apicid value is greater than
MAX_APICS, then we need to decrement the number of valid processors
before we return (the number was just incremented before the check.)

The patch was written by James Cleverdon.

Simple compile fix.

Another from 2.4, see comments for details

Push BKL down to the (few) routines that actually need it,
remove it from the do_exit() path.

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

ttl of tcp_socket.

brw_kiovec() and ll_rw_kiovec() switched to struct block_device *.

Bunch of places converted from fsync_dev/invalidate_buffers to
fsync_bdev/invalidate_bdev.

get_sb_bdev() stores original block size in ->s_old_blocksize and
kill_block_super() restores it.

This kills 99% of crap with "oh, I've mounted/umounted that device and
its behaviour had changed" (remaining 1% can be dealt in pretty similar
ways; ideally I'd like to see ioctls that get/set block size dead and
gone).

Fix typo

Use sb_set_blocksize() in JFS instead of trying to do it by hand.

Clean up minix/bitmap.c

Kill BKL in minix/itree* (similar to ext2 patches)

Clean up the write_super-related code in minixfs

Move minix-private stuff to fs/minix/minix.h.

This version of sys_nfsservctl() fix hadn't made DaveM complain.

Obvious romfs fix.

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

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

In 2.5.7 there is a thinko in the allocation and initialisation
of the fs-private superblock for ext2.  It's passing the wrong type
to the sizeof operator (which of course gives the wrong size)
when allocating and clearing the memory.

Lesson for the day: this is one of the reasons why this idiom:

	some_type *p;

	p = malloc(sizeof(*p));
	...
	memset(p, 0, sizeof(*p));

is preferable to

	some_type *p;

	p = malloc(sizeof(some_type));
	...
	memset(p, 0, sizeof(some_type));

I checked the other filesystems.  They're OK (but idiomatically
impure).  I've added a couple of defensive memsets where
they were missing.

- Apply Pavel Macheks suspend resume double resume fix.

- Finally remove the busy field for ata_operations and replace it with
   MOD_INC_USE_COUNT and MOD_DEC_USE_COUNT.

- Fix ali15xx chipset support by removing initialization differences,
   apparently caused by mislead interpretation of the specs or a mismatch
   between the specification and reality.

- Guard calls to ide_set_handler with checks to see whatever the previously
   installed IRQ handler already served it's purpose.

- Convert timeout checks on poll_timeout to the time_before() interface.

- Consolidate the two different IRQ handlers for multi mode PIO writes into
   one. The problems remain the same but at least now we will only have to
   tangle one single problem.

- Make for less terse error messages in ide-tape.c.

- Replaced all timecomparisions done by hand with all the proper timer_after()
   commands.

- Remove the drive niec1 mechanisms alltogether. There are several reasons for
   this:

   1. The code implementing it is nonintelliglible and therefore propably
   broken.

   2. If we have to invent somethig about sceduling drive IO, it should be done
   on the BIO level.

   3. We may in fact interleave with the IO sceduling on the upper layers and
   the results of two overlapping signal filters overlapped with each other can
   be disasterous to the overall throughput. (In fact they *are* most of the
   time.)

   4. It was not working if you had intermixed modes on different drives
   DMA versus PIO.

   5. Our goal is to have a driver which is able to share the badwidth
   properly and shouldn't needing this kind of "tuning".

- Remove unused nice2 from disk struct.

- Rename channel member of ata_channel to unit and device to dev to
   just prevent wrong interpretations. This prevents constructs like
   channel->channel...