USB host controllers and Device 12fd 1001 (aincomm awu2000b or IBlitzz BWU613B)

Enver Haase ehaase at inf.fu-berlin.de 
reported that he managed to make the  Device 12fd 1001 (aincomm
awu2000b or IBlitzz BWU613B) work.  That's great news!
I've been struggling to accomplish this since Dec. 2003 without 
success.

This was achieved with "kernel 2.6.4 using the "berlios" driver",
but no other details were offered.  It would be helpful to know
exactly what was done.

I am working with Fedora Core 1, kernel 2.4.22-1.2174.nptl, and
at76c503-0.11.tar.gz.  The vendor/product numbers reported by my
Blitzz BWU 613B device of 0x12fd and 0x1001 are not known in any 
of the drivers of this package so the USB device is not "claimed"
by any driver.  I have tried adding these lines to at76c503-rfmd.c

#define VENDOR_ID_BLITZZ              0x12fd
#define PRODUCT_ID_BLITZZ_BWU613B     0x1001 /* Blitzz BWU613B buy 12/03 */

        { USB_DEVICE(VENDOR_ID_BLITZZ,   PRODUCT_ID_BLITZZ_BWU613B ) },

This allows the driver to recognize the device and configure wlan0.
However, no radio communication occurs.  Pinging another Ad-Hoc
station by IP number generates activity on the wlan0 interface,
but the other station hears nothing.  Pinging in the opposite
direction also produces no reception in the Blitzz device.
'ifconfig wlan0' reports transmitted packets but zero received packets.

Since I don't know what's inside this device, I tried adding the
Blitzz parameters to each of the six possible drivers in turn.
Once in a while the at76C505-rfmd2958 driver would seem to recognize
the device, but it wouldn't communicate.

Has anyone succeeded in making the Blitzz USB wireless device work?
If so, how?  Thanks.

-- 
	David A. De Graaf    DATIX, Inc.    Hendersonville, NC
	dad-ucVp/[email protected]    (828) 696-8646;  fax (828) 694-1037