Add driver for multi-subchannel devices (ctc and lcs)

The cu3088 driver is an metadriver to make the ctc and lcs
(potentially also claw) drivers work with the new
channel subsystem driver. It uses the ccwgroup driver to
group subchannels for ctc and lcs.

Authors:
	Arnd Bergmann <arndb@de.ibm.com>
	Cornelia Huck <cohuck@de.ibm.com>

Rework of tape driver

  Almost complete rewrite of the s390 tape driver code by
  Martin Schwidefsky. Skipping the 2.4 era, this makes the tape
  code ready for the future.

  This driver probably doesn't have to change much before 2.6.

Authors:
	Martin Schwidefsky <schwidefsky@de.ibm.com>
	Stefan Bader <shbader@de.ibm.com>

Convert dasd driver to new channel subsystem driver

This makes the dasd driver work again after the changes to
the channel subsystem driver:
- handle device detection with standard driver model functions
- reduce use of dasd_devmap (devmap will die as soon as
  dasd configuration is handled from initramfs)
- some cleanups

Authors: Arnd Bergmann <arndb@de.ibm.com>
	 Martin Schwidefsky <schwidefsky@de.ibm.com>

Update iucv driver for new driver model

iucv device configuration is now done through sysfs instead of /proc

Author: Cornelia Huck <cohuck@de.ibm.com>

Convert 3215 console driver to new channel subsystem driver

this adds support for the driver model to the 3215 driver. The console
is one of the biggest problems because the regular device detection
is now done at initcall time although we actually want full
support for channel attached console devices as early as possible.
con3215_init() now uses a special ccw_device_probe_console() function
to do an early initialization of a single device.

The main backdraw for users is that the console can no longer
be autodetected when not running under VM. LPAR or P390 users
with a channel attached console now have to specify
console_device=f00 as a kernel parameter.

Authors:
	Martin Schwidefsky <schwidefsky@de.ibm.com>
	Arnd Bergmann <arndb@de.ibm.com>

Documentation changes for common i/o.

ccwgroup bus driver.

The ccwgroup driver contains 'ccw_group' devices, which needed because of
strange hardware properties: Some device drivers need two or more
ccw_devices to make up a logical device and the user has to configure
which ones belong together. We have not found a way to represent this
correctly using the linux driver model, the current implementation
is about as good as it gets.

Authors: Arnd Bergmann <arndb@de.ibm.com>,

Rewrite of the s390 channel subsystem driver for the new driver model

The channel subsystem driver a.k.a s390 common I/O layer is the low level
driver for most device drivers on s390 systems. The old code is largely
unchanged from the initial linux-2.2 port and there is a lot of bitrot
on it.

In particular, concepts from the 2.5 driver model are implemented in a
completely different and more complicated way here.
This rewrite tries to get the driver ready for 2.6. The new interface is
not compatible to the old one but should be rather stable now unless
someone finds major flaws.

The 's390dyn' and 'chandev' interfaces have been removed entirely (yippii!)
and are replaced by hotplug and sysfs interfaces.

Authors: Arnd Bergmann <arndb@de.ibm.com>,
         Cornelia Huck <cohuck@de.ibm.com>,
         Martin Schwidefsky <schwidefsky@de.ibm.com>

Remove channel device layer.

s390 debugging documentation update.

Add missing include.

Add additional parameter for do_fork.

Make debug feature less noisy.

Add s390 elf relocations.

Move clearing of .bss before the memory detection loop to avoid
problem when compiling with gcc 3.3.

New configuration options DEBUG_KERNEL, DEBUG_SLAB, KALLSYMS and
DEBUG_SPINLOCK_SLEEP. Update default configuration.

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

using the new system call restart infrastructure.

This breaks the compat layer - it really needs to do its own version
of restarting, since the restarting depends on the types.

handling.

Update x86 to use the new infrastructure.

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

into kroah.com:/home/greg/linux/BK/pnp-2.5

This trivial patch updates the gameport driver to the new id scheme.

This contains three changes.  The first removes some #defines that don't
seem to be needed anymore.  The second fixes a problem when CONFIG_LBD
is set and sector_t is u64.  The third fixes some compile warnings
setting a char * in the scsi_pointer struct to a dma_addr_t.  I changed
the usage from the ptr element to the dma_handle element.

It compiles without warnings and I have run some tests on aacraid devices
on the osdl lab machines with the CONFIG_LBD option on and off.

I forgot the errno.h.  Without this patch, things may not compile when
pnp support or pnp card support is disabled.

Hope you had a good trip.  I noticed a small mistake in pnp 0.93 and I have
a fix for it.

Attached is a patch, that updates the 2.5.50 to the latest pnp
version.  It includes all 9 of the previously submitted patches.

Highlights are as follows:
-PnP BIOS fixes
-Several new macros
-PnP Card Services
-Various bug fixes
-more drivers converted to the new APIs

This simplifies logic in acpi_wakeup.S by putting code and data into
same segment. Plus it kills off-by-3 bug and uses constant instead of
hardcoded value.

When kernel becomes too big, table allocated in acpi.c is no longer
big enough and machine crashes during acpi_wakeup.S... This fixes
it and adds safety check for acpi_wakeup's code size.

This adds basic support to md.c.

This makes swsusp 64bit compatible, and makes it work in case of two
mirrors of physical memory (x86-64 works like that). It also contains
few accumulated cleanups.

swsusp: Move loop variables into assembly, where they are used.

This moves CONFIG_SOFTWARE_SUSPEND where it belongs, and makes
ACPI_SLEEP depend on it to prevent compile problems.

From:  Chris Wilson <chris@qwirx.com>

  If the call to devfs_register() fails, then the driver does not deregister
  its misc device before returning an error. This should fix it.

From:  william stinson <wstinson@wanadoo.fr>

  	1) removes one call to check_region
  	2) uses request_region instead
  	3) calls release_region in case of driver initialisation error later on

From:  Michael Still <mikal@stillhq.com>

[ Return error from misc_register-002-002, not some random value ]
From:  Michael Still <mikal@stillhq.com>

From:  Paul <set@pobox.com>

From:  Brad Hards <bhards@bigpond.net.au>

From:  Stephen Rothwell <sfr@canb.auug.org.au>

  Every definition if sigmask() was the same.  In one case it was
  mutilply defined for the arm architecture.  This patch removes all the
  architecture defines of sigmask and moves the generic define from
  the protection of __HAVE_ARCH_SIG_BITOPS.