Here is the usblp buffer allocation patch for 2.5.47.

This was suggested by Max Krasnyansky to try to remove confusion between this driver
and the BlueZ supported driver.

Bad news is that the scanner endpoint change did not work, maybe I
mistested it or it never worked. My version worked, but was very ugly.

Here is a working one (against 2.5.47), this also looks nicer (I did not know the
EP_XXX() could be changed too):

What it does is give up on catching all the "race with HC" cases
when appending to a live QH, by switching to using a disabled
"dummy" TD at the end of all hardware queues.  The HC won't cache
disabled TDs, so it just sees "always good" pointers: no races.

As a side benefit this also makes it safe to not irq on completion
of most TDs that are queued using the scatterlist calls, so it'll
be typical for one 64 KByte usb-storage request to mean just one
irq (or less!) even without tuning ehci irq latency (for the DATA
stage, that is).

Mostly just highlights the PDA support, now that we can say
this talks to all the Linux based PDAs; adds "more info" URL.

This adds some simple unlink test cases.  I've only run these
against OHCI so far, and so far only in simple configurations
(only one active device), where it hasn't yet turned up problems.

This fixes <linux/device.h> so dev_warn() uses KERN_WARNING,
instead of a non-existent symbol.  It also uses parens around
some arguments that need them ... those macros are now usable.

This patch removes the special-case code for START_STOP.  It can be safely
removed now because the higher SCSI layers won't send this command unless
the device indicates that it needs it to allow media access.

This patch fixes some spelling errors and makes some comments a bit
more clear.

This patch fixes the case of an ABORT happening during the auto-sense
processing when using the ISD-200 driver.

Once upon a time, the SCSI command structure could only hold a maximum of
12 bytes.  Thus, the ISD-200 driver needed an entirely separate function to
work with 16-byte commands.

Now that 16-bytes is stored, we can cut the duplicates.

Since we now test for aborts at a higher level, the low-level end of the
drivers don't need to be constantly testing for aborts.  This patch removes
that excess logic.

(Yes, they should probably use __stringify() instead).

This patch provides basic x86 support for modules.

This is an implementation of the in-kernel module loader extending
the try_inc_mod_count() primitive and making its use compulsory.
This has the benifit of simplicity, and similarity to the existing
scheme.  To reduce the cost of the constant increments and
decrements, reference counters are lockless and per-cpu.

Eliminated (coming in following patches):
 o Modversions
 o Module parameters
 o kallsyms
 o EXPORT_SYMBOL_GPL and MODULE_LICENCE checks
 o DEVICE_TABLE support.

New features:
 o Typesafe symbol_get/symbol_put
 o Single "insert this module" syscall interface allows trivial userspace.
 o Raceless loading and unloading

You will need the trivial replacement module utilities from:
	http://ozlabs.org/~rusty/module-init-tools-0.6.tar.gz

By Kai Germaschewski.

This patch adds a -DKBUILD_MODNAME to the kernel compile, which
contains the base of the module name which is being built.

 - Some sreorganization of the c_flags since they're needed for
   generating modversions (.ver) and compiling
 - Use the right KBUILD_MODNAME also when the user just wants a .i/.s/.lst
   file for debugging and also when generating modversions
 - It looks like with your current approach you can't have a ',' or '-' in
   KBUILD_MODNAME - however, that means that KBUILD_MODNAME is not quite
   right for passing module parameters for built-in modules on the command
   line, it would be confusing to pass parameters for ide-cd as
   ide_cd.foo=whatever. So that part could use a little more thought.
 - If you think your module_names trick makes a noticable difference, feel
   free to re-add it.
 - It's possible that objects are linked into more than one module - I
   suppose this shouldn't be a problem, since these objects hopefully
   don't have a module_init() nor do they export symbols. Not sure if your
   patch did handle this.

 - compile fixes in amiflop.c
 - removal of dead local variables in ll_rw_blk.c
 - removed gratitious devfs_get_handle() in usb/input/hiddev.c
   (no need to do lookup for "usb" and then create "hid" in
   there - enough to create "usb/hid" at once).

dasd.c forgot to set ->private_data, but was using it ;-/  Fixed.

Remaining dasd_devmap_from_kdev() callers switched to
dasd_devmap_from_bdev() (other than call from dasd_devmap_from_bdev(),
that is).

dasd_devmap_from_kdev() merged into dasd_devmap_from_bdev().

Eliminated several gratitious ->bd_dev uses.

Bunch of kdevname() uses replaced with bdevname().

__bdevname() switched from kdev_t to dev_t; callers updated.

Compile fixes, cleanup.

RAID autoconfig rewritten to use syscalls and moved into do_mounts.c;
use of devfs_get_handle() in do_mounts.c also rewritten in syscalls.