USB usbnet driver update

The patch cleans up the handling of connection checking to
match the truth that it's effectively tristate (connected, not,
and can't know) vs binary ("connected" and "can't know"
as the same value, since it was OK to ifup).  Since ethtool
supports the tristate semantics, it matters now.

	- Modified port open, port close, and send setup() logic to fix various data and endpoint
	  synchronization bugs and device LED status bugs.
	- Changed keyspan_write_room() to accurately return transmit buffer availability.
	- Changed forwardingLength from 1 to 16 for all adapters.

Here's a patch that finishes off my previous patch that enabled us to
use less than 16 minor numbers per USB device that uses the USB major
number.  This patch allows all such devices to share all 256 minor
numbers at once, much like the usbserial core shares the USB serial
major with all usb-serial drivers.  This also solves Oliver's problem of
having 30 printers :)

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

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

This patch is the result of that discussion a short while back
to fix the "hub driver polls too quickly at high speed" bug.

    - redefines "interval" of usb_fill_int_urb() to be what
      the endpoint descriptor returns, and transparently
      does the log-to-linear conversion if it's high speed

    - (most of the patch by volume!!) moves declarations
      forward so testing dev->speed there will compile.

No driver changes were needed -- most drivers pass the
endpoint bInterval value already, and those that don't are
not dealing with high speed device quirks.

p.s. Includes an unrelated one-liner:  deletes export of
    usb_inc_dev_use() so it now shows up in kernel doc.
    Minor oversight in an earlier patch.

USB set_bit() and friends now need a long paramater

Fixes the set_bit() warnings in the ehci and ohci driver

This patch fixes up some lose ends left over from the last x86-64 jumbo merge.

 - make it compile again. ia32_ioctl was referencing IDE ioctls that got
   remove in a merge race
 - Use the memset/FXRSTOR way to initialize the FPU, as discussed.
 - Fix semctl/shmctl ABI (thanks to Andreas Schwab)
 - Other minor fixes.

  This fixes compile errors.  It has been tested with a weekend of Bonnie++ 8GB
runs on a RAID0 setup at the OSDL.  This was built against and tested on 2.5.8
and applies cleanly to 2.5.9.

  LSI told me they have a version 2.0 of the driver in development but
it would be really nice to have the dang thing working now ;-)

Fix a few spelling mistakes in documentation (arch/i386/boot/setup.S,
Documentation/sysrq.txt).

Move BKL into the fs-specific write_super()'s.

As we discussed some time ago, here is a patch for the SEM_UNDO change
that can be applied to linux-2.5.9.

warnings for proper usage.

No object-code changes, but removes warnings from the stricter
typechecking.

Now it really works (I tried).

USB pegasus driver

  SOHOware NUB110 addet to the support list

changed the number of minor devices the braille voyager driver uses.

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

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.make

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.make

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

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.isdn

As a result of the recent BKL removal in notify_change, nfsd_symlink
downs the inode semaphore twice (the first time is in fh_lock).

fixed a few times too many already ;)

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

- Make the ide-cd driver usable again in DMA mode by adapting it to the TCQ
   related request handling changes and fixing some other minor stuff related to
   this. This patch is ugly like hell I know. Cleanup will follow separately.
   It was hard enough to make this going agian at all.

in /etc/kernel-config, and only if that fails in the architecture-
specific defconfig.

USB fix documentation bug

 After some source investigations I discovered a harmless mistake:
 The description of the  usb_control_msg(...) function says
 it returns 0, or less than 0 if an error occured, but
 the usb_internal_control_msg returns length, which is sometimes >0
 (success) or <0 if error.