On Wed, Aug 15, 2007 at 07:59:51AM +0200, Ulrich Kunitz wrote:
>> Vendor:         Shuttle
>> Model:          PN18G (although it doesn't seem to be marked as such)
>> USB Device ID:  07b8:6001
>> Chip:           ZD1211B
>> RF:             AL2230S


>> 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 see.  So, the only apparent solution is to notify Atheros of the problem, and
hope that they chastise the module manufacturer appropriately?

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

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

It wouldn't be something you could find in /proc/bus/usb/devices, would it?

>> 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.

Clearly :)  Sorry for stating the obvious.

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

Ah, so you can't use a EAFP/trial-and-error approach (and LBYL is not an option
due to the chip not making any mechanism available by which it can be

Forest Bond

Attachment: signature.asc
Description: Digital signature

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