Console drivers cleanup.  In current tree interaction between
console and tty layer sits in the ->device() method of struct console.
It takes a pointer to console and returns device number of its tty
device.  open(2) on /dev/console goes through the list of registered
consoles, picks the first one that has ->device() and remaps the device
number to console->device(console).  Then it proceeds with normal
opening of tty.  This is the only caller of ->device().

	Cleanup: let ->device() return a pair (pointer to tty_driver, index
of tty in question) instead of device number.  Note that
	a) the first thing tty_open() does with remapped device number is
conversion to such pair.
	b) console driver _knows_ which tty_driver we want - one that
implements tty interface to the same physical device (i.e. the part of
the same driver).
	c) current code expects the result of ->device() to be a device
number of tty device - anything else is immediate -ENODEV from tty_open();
might as well have NULL ->device in that driver.

	Console drivers converted, (the only) caller updated.

	Preparation to console->device() cleanup: serial drivers converted
to common helper for their ->device() methods.

Don't disable the Northbridge Machine Check.

Use the unrolled "INTEL_USERCOPY" too.

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

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

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

into nuts.ninka.net:/home/davem/src/BK/net-2.5

Linus, could you please apply this patch so all thos poor devfs
users get their disks back?

The patch is obviously correct and has been floating on lkml for some time.

From Manfred Spraul:
 "My init_irq cleanup introduced a bug: on error, the function must return 1."

Looks like my finger fell off the control key..

Fix some warnings from the new code-patching stuff.

- Fix printk bug in the diagnostic code.

- If an error occurs, print the address of all the offending action
  handlers.  Also the symbol name if CONFIG_KALLSYMS.

The invalidate_buffers in ->release is wrong, get a reference to the
discipline in the beginning of ->open.

This one probably crept in during an ide merge from 2.4..

It looks like no one even tried to use it on 2.5..

Return an error code instead of a devfs_handle_t.  The handle isn't
useful for anything and the !CONFIG_DEVFS_FS stub in fact returned
NULL which made it entirely useless.  Thus only one driver is actually
checking the retval in the current tree..

Now that devfs_handle_t is gone from all structs there is no
reason to include it in headers.

Fix the fallout by including previously implicit headers and fixing
the drivers that didn't include devfs_fs_kernel.h explicitly.

They are obsfucating aliases for SetPageReserved/ClearPageReserved.
And once they're gone we can nuke <linux/wrapper.h>

And uninline end_request - it's calling to many functions to be useful
inline.

They don't have any code in common, so the initrd support can
go into a separate file and not require ramdisk support.

Lots of ifdefs gone and smaller kernel images for initrd users.

not be marked __init.

Noted by Petr Vandrovec

	* we allow tty_driver to cover more than 256 devices
	* pty.c cleaned up - now we only one driver for UNIX98 masters and
only one driver for UNIX98 slaves, so a lot of ugliness can be killed.
	* get_tty_driver() became an analog of get_gendisk() - it does
a lookup by device number and gives (pointer to tty_driver,index).
	* registration/unregistration of tty_driver updated
	* /proc/tty/drivers code updated (now one structure can be responsible
for several lines)

	tty->device switched to dev_t
	There are very few uses of tty->device left by now; most of
them actually want dev_t (process accounting, proc/<pid>/stat, several
ioctls, slip.c logics, etc.) and the rest will go away shortly.

Preparations to cleanup:
	* call of get_tty_driver() moved from init_dev() to its callers
	* instead of kdev_t dev we pass struct tty_struct *driver and int index

	* drivers/char/rio/* supports up to 4 boards, each with up to 128
lines.  It used to share termios for 1st/3rd and 2nd/4th boards,  Fixed.
	* cleanups and kdev_t removals - we pass tty instead of tty->device
in a couple of helper functions and instead of comparisons on major(tty->device)
we check where does tty->driver point to.

	* generic_serial.c typo fix (->driver used instead of correct
->driver_data)
	* tubio cleaned up

	sanitized driver->driver_name initialization and use

	tty->tty_index added; we initialize it with minor(tty->device) -
tty->driver->minor_start.  Majority of remaining tty->device uses had
that form and are switched to use of tty->index.

	new field - tty->tty_name;
	initialized to <driver->name><tty index+driver->base_name>
when we allocate tty_struct.  Drivers code switched to use of that
beast (in debugging printks, mostly).  Large, but trivial.