> Vendor:         Shuttle
> Model:          PN18G (although it doesn't seem to be marked as such)
> USB Device ID:  07b8:6001
> Chip:           ZD1211B
> RF:             AL2230S
> The chip description from dmesg:
> [ 1378.268000] zd1211rw 5-6:1.0: zd1211b chip 07b8:6001 v4810 high 00-12-0e 
> AL2230S_RF pa0 -----
> It is a USB device designed to be connected directly to a pin header or other
> internal connector.  It has the large coax antenna mount, and also provides an
> alternative U.FL connector that a pigtail may be attached to.

I know it, I have the older product in my Shuttle. (Actually this
was the device that started me to go into this.)

> Anyway, it looks like this is a re-use of a previously existing device ID.  I
> had to modify the driver to get it working (patch attached).

We have seen this now several times. Zydas/Atheros told us that
this shouldn't happen, because this was the only method, we have
been aware to distinguish between both products.

> I hope this is enough info to get this working in mainline.

Not really, we need to find another way to identify the chip.

> BTW, it would be nice if the driver printed an error message if a ZD1211 is
> assumed but the chip is actually a ZD1211B, or vice-versa.  It currently fails
> silently.  I'm not sure if there is a good way to determine at runtime what 
> kind
> of chip you are actually talking to ... ?

That's exactly the problem. The problem is also that resetting the
device doesn't work reliably. We need to work on it.

>  static struct usb_device_id usb_ids[] = {
>       /* ZD1211 */
>       { USB_DEVICE(0x0ace, 0x1211), .driver_info = DEVICE_ZD1211 },
> -     { USB_DEVICE(0x07b8, 0x6001), .driver_info = DEVICE_ZD1211 },
> +    /* Work-around for Shuttle PN18G, which re-uses this device ID: */
> +     { USB_DEVICE(0x07b8, 0x6001), .driver_info = DEVICE_ZD1211B },
>       { USB_DEVICE(0x126f, 0xa006), .driver_info = DEVICE_ZD1211 },
>       { USB_DEVICE(0x6891, 0xa727), .driver_info = DEVICE_ZD1211 },
>       { USB_DEVICE(0x0df6, 0x9071), .driver_info = DEVICE_ZD1211 },

Uli Kunitz

This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

Reply via email to