Forgot to CC the list, sorry. (What happened to "Default Reply to All"?)
2009/6/18 G?bor Stefanik <[email protected]>:
> This appears to be the same as
> http://osdir.com/ml/network.wireless.zd1211.devel/2007-07/msg00038.html
>
> However, I can't actually find any trace of non-B ZD1211s with this ID.
>
> On Thu, Jun 18, 2009 at 5:54 PM, Pascal Terjan<[email protected]> wrote:
>> On a shuttle machine here we got 07b8:6001 device, handled by zd1211rw, which does not work.
>> Scanning is OK but association does not work, we get "direct probe to AP xxx timed out"
>>
>> It appears that this simple patch makes the device work perfectly.
>>
>> This id was already there in initial import of the driver so I don't know if it has ever been
>> working as ZD1211 (which would mean they changed it and kept the id :( ).
>>
>> Signed-off-by: Pascal Terjan <[email protected]>
>> ---
>> ?drivers/net/wireless/zd1211rw/zd_usb.c | ? ?2 +-
>> ?1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/net/wireless/zd1211rw/zd_usb.c b/drivers/net/wireless/zd1211rw/zd_usb.c
>> index f0e5e94..d04a69d 100644
>> --- a/drivers/net/wireless/zd1211rw/zd_usb.c
>> +++ b/drivers/net/wireless/zd1211rw/zd_usb.c
>> @@ -38,7 +38,6 @@ static struct usb_device_id usb_ids[] = {
>> ? ? ? ?/* ZD1211 */
>> ? ? ? ?{ USB_DEVICE(0x0ace, 0x1211), .driver_info = DEVICE_ZD1211 },
>> ? ? ? ?{ USB_DEVICE(0x0ace, 0xa211), .driver_info = DEVICE_ZD1211 },
>> - ? ? ? { USB_DEVICE(0x07b8, 0x6001), .driver_info = DEVICE_ZD1211 },
>> ? ? ? ?{ USB_DEVICE(0x126f, 0xa006), .driver_info = DEVICE_ZD1211 },
>> ? ? ? ?{ USB_DEVICE(0x6891, 0xa727), .driver_info = DEVICE_ZD1211 },
>> ? ? ? ?{ USB_DEVICE(0x0df6, 0x9071), .driver_info = DEVICE_ZD1211 },
>> @@ -86,6 +85,7 @@ static struct usb_device_id usb_ids[] = {
>> ? ? ? ?{ USB_DEVICE(0x0471, 0x1237), .driver_info = DEVICE_ZD1211B },
>> ? ? ? ?{ USB_DEVICE(0x07fa, 0x1196), .driver_info = DEVICE_ZD1211B },
>> ? ? ? ?{ USB_DEVICE(0x0df6, 0x0036), .driver_info = DEVICE_ZD1211B },
>> + ? ? ? { USB_DEVICE(0x07b8, 0x6001), .driver_info = DEVICE_ZD1211B },
>> ? ? ? ?/* "Driverless" devices that need ejecting */
>> ? ? ? ?{ USB_DEVICE(0x0ace, 0x2011), .driver_info = DEVICE_INSTALLER },
>> ? ? ? ?{ USB_DEVICE(0x0ace, 0x20ff), .driver_info = DEVICE_INSTALLER },
>> --
>> 1.6.2.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to [email protected]
>> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>>
>
>
>
> --
> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
2009/6/18 G?bor Stefanik <[email protected]>:
> Forgot to CC the list, sorry. (What happened to "Default Reply to All"?)
>
> 2009/6/18 G?bor Stefanik <[email protected]>:
>> This appears to be the same as
>> http://osdir.com/ml/network.wireless.zd1211.devel/2007-07/msg00038.html
>>
>> However, I can't actually find any trace of non-B ZD1211s with this ID.
Argh -- I think it is probably a good idea to stick a comment next to
that id saying it might be in the other section. (i.e. put this next
to the code). This is an instance where some punishment of the
manufacturer is deemed appropriate :-).
FWIW, Epson uses the same product id for both their stylus inkjets and
their cheap EPL laser printer series :-). Luckily, it is usually quite
obvious which one is which from just looking at the device... if the
user can be confused by that, he/she should not be allowed near a
printer...