USB net drivers, ethtool bus_info

This patch makes the USB network drivers that have ethtool support
expose only those stable IDs ... no more references to unstable values
like dev->bus->busnum (changes depending on order of modprobe)
or dev->devnum (assigned not quite randomly during enumeration :).

This supports more intelligent policies for user mode tools, such
as "always assign this address to the device on that port", as well
as making troubleshooting more practical when there are multiple
devices (of a given type) present ... you can tell which is which.

This provides something that gets discussed regularly: stable
device IDs.  Straightforward; most of it was already present:

    - Moves "bus_name" out of HCD framework into usb_bus.
      This accounts for _by far the bulk_ of this patch, since
      every use of that original field needed to change.

    - Make Vojtech's usb_make_path() use bus_name instead
      of unstable bus numbers ... and usb_device->devpath
      instead of recomputing that same info.  Combine two
      stable IDs, and the result is still stable.  And since both
      are precomputed, usb_make_path() turns into only an
      error check wrapped around snprintf() ... so I inlined it.

    - Minor tweak to usb_device->devpath construction.  It
      still uses "/" for the root hub (better suggestions?) but
      Vojtech wanted "." for separators, so I changed that.

    - The older HCDs (uhci.c etc) initialize usb_bus.bus_name,
      as well as the sharable HCD framework

    - HCD framework no longer uses "bus" member.

These IDs are currently exposed in "input" hotplugging, and
my next patch addresses that for USB network devices.

cleaned up the comments to put them in proper docbook format.

sanity checking and cleanup on device disconnect.
  
    - Splits apart usb_dec_dev_use(), for driver use, and
      usb_free_dev(), for hub/hcd use.  Both now have
      kerneldoc, and will BUG() if the refcount and the
      device tree get out of sync.  (Except for cleanup of
      root hub init errors, refcount must go to zero only
      at the instant disconnect processing completes.)
  
    - More usbcore-internal function declarations are
      now moved out of <linux/usb.h> into hcd.h
  
    - Driver-accessible refcounting is now inlined; minor
      code shrinkage, it's using atomic inc/dec instructions
      not function calls.

<note from greg k-h, there is still some work to be done with USB device
 reference counting, but this patch is a step in the right direction.>

This fixes some kerneldoc bugs for USB.  It catches up with
the recent rename, and includes a couple minor tweaks/fixes
I happened to notice.

renamed the bluetooth.c file to bluettty.c to help prevent user confusion
between this driver and the bluez bluetooth stack in the kernel.

This was originally created by David many months ago and posted to the
list, but not put into the kernel.

I modified the original patch to:
-patch against the 2.5.7 kernel
-use the 'real' interface number, not position (to do this I added 2
 methods in usb.c)

Here is an updated patch using kmalloc that removes the page limit
on bulk transfers in usbfs.  I've tested it and it seems to work OK.

Thanks to Paul Komkoff for reminding me of this.

The dangers of not ensuring important fields are properly set.

Some, if not all, of the speed problems with uhci.c were caused because
some important fields were not set and as a result, FSBR was never
turned on.

This patch also ensures is_suspended is set to 0 properly. This could
cause some problems suspending the HC when no devices are plugged in.

This fixes a problem that I've not run into and is difficult to trigger,
but definately a bug. We locked urb->lock, when we meant u->lock. It also
cleans up the code a little to make it easier to understand and removes
an obsolete comment.

This patch merely cleans up the code a little and doesn't fix any bugs.
It makes a couple of code paths a bit easier to understand, removes an
unused variable (uhci_list) and some procfs variables when not using
procfs.

This patch fixes a bug reported by Greg and David, as well as some other
people recently.

uhci.c would call wait_ms, which can sleep, with spinlocks held. There
are two places where this happens, but only one was the cause of the
problem.

spilt up the Config.help file into smaller pieces

    - adds ethtool support (based on code from Brad Hards)
    - makes diagnostic level configurable (ethtool, module param)
    - fixes a minor mem_flags goof (thanks Oliver!)
    - device identifers now use devpath (stable ID) not devnum

This chunk is present in 2.4, missing in 2.5.  It
stops the loop thread from waiting on its owm buffers.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

It's up to other architectures to worry about portability for now.

Moved i_sem down into notify_change() and out of the UMSDOS
function. Moved BKL down from notify_change into filesystems.

typo in that last patch, sorry.

This increases the max read/write size for nfsd from 8K to 32K.

This requires making NFSv2 return the right number in statfs
requests.  NFSv3 already does that.

[PATCH] PATCH 3 of 4 : knfsd : Store the fsid in the returned attributes instead of the device number

When a filesystem is exported with  fsid=  we should use that
fsid instead of the i_dev number when returning NFS attributes,
so that there is no chance of clients that depend on the filesys
id in the attributes getting confused by device numbers changing.

We only do this if the reference filehandle uses fsid to identify
the filesystem, so that a server can be converted from non-fsid= to
using fsid= without confusing active clients.

Previously we could only export FS_REQUIRES_DEV filesystems
as we need a devno to put in the filehandle.
Now that we have fsid= (NFSEXP_FSID) we don't need a devno
to put in the filehandle so we can relax this requirement.

Use symbolic names for some common size components in the response
size calculation for the NFSD.  This makes it easier to get the
numbers right and to review them.
This patch also fixes a few number for nfsv3 that were wrong.

Lets just kill this check -- it usually only catches drivers queueing
something in front of a started request on their own (such as shoving a
request sense in front of a failed packet command, for instance). So
it's either working around this detection in some drivers, or killing
it. I vote for the latter, patch attached against 2.5.8-pre1 :-)

moved the USB_STORAGE Config.help items into the drivers/usb/storage directory.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

added a README file to explain what the different subdirectories are for.

moved class/storage/ back to storage/
created input/
orderd the makefiles and config.in menus better.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

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