On Tuesday 31 July 2007, Andy Green wrote:
> Somebody in the thread at some point said:
>
> >> + /* BlueNEXT */
> >> + { USB_DEVICE(0x148f, 0x2573), USB_DEVICE_DATA(&rt73usb_ops) },
> >
> > This USB ID is already in the List under the Label "Ralink"
> >
> > /* Ralink */
> > { USB_DEVICE(0x148f, 0x2573), USB_DEVICE_DATA(&rt73usb_ops) },
>
> Gah! I guess I jumped to the wrong conclusion when it didn't work,
> because rt2500usb.ko also claims this ID. Blacklisting rt2500usb and
> "adding" the ID in rt73usb got me able to do monitor mode, but I guess
> blacklisting rt2500usb was what did the trick.
:)
> Sorry for the noise, but maybe the same ID in rt2500usb should be
> removed, unless there is some story here about ID reuse...
Unfortunately there have been reports about devices with that USB ID
that contains a rt2500usb chipset. There are a number of duplicate USB ID's
between rt2500usb and rt73usb.
Some manufacturers like to release new revisions of their wireless USB stick
with different chipsets but with the same USB ID.
Ivo
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
