[rt2x00-users] Unknown Ralink Device Vid: 148f Pid:5370

[Gertjan van Wingerde]

On 04/20/11 21:39, Juan Carlos Garza wrote:
> Hi again,
> 
> On Wed, Apr 20, 2011 at 8:10 PM, Gertjan van Wingerde
> <gwingerde at gmail.com> wrote:
>> On 04/20/11 19:31, Juan Carlos Garza wrote:
>>> Hi,
>>>
>>> On Wed, Apr 20, 2011 at 6:43 PM, Gertjan van Wingerde
>>> <gwingerde at gmail.com> wrote:
>>>> Hi Juan Carlos,
>>>>
>>>> On 04/20/11 18:21, Juan Carlos Garza wrote:
>>>>> Hi all,
>>>>>
>>>>> I just got a Ralink USB dongle with the following characteristics:
>>>>>
>>>>>
>>>>> T:  Bus=01 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#=  6 Spd=480 MxCh= 0
>>>>> D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
>>>>> P:  Vendor=148f ProdID=5370 Rev= 1.01
>>>>> S:  Manufacturer=Ralink
>>>>> S:  Product=802.11 n WLAN
>>>>> S:  SerialNumber=1.0
>>>>> C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=450mA
>>>>> I:* If#= 0 Alt= 0 #EPs= 7 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>>>>> E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>> E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>> E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>> E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>> E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>> E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>> E:  Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
>>>>>
>>>>> I tried to quickly add the Vid and Pid into the rt2800usb.c file and
>>>>> see if it was just
>>>>> some Pid changed, but no success, the driver rejects it.
>>>>>
>>>>> phy5 -> rt2800_init_eeprom: Error - Invalid RF chipset detected.
>>>>> phy5 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
>>>>>
>>>>> The supplier claimed that it was a 3070 chip (which I seriously doubt).
>>>>>
>>>>> Anyway, the supplied driver is basically the staging driver that can
>>>>> be downloaded,
>>>>> and it seems to be compatible with the RT2870 firmware.
>>>>>
>>>>> What can you tell me about it? If it indeed is compatible with the
>>>>> rt2800usb driver,
>>>>> how much effort would it be needed to include it?
>>>>>
>>>>
>>>> This seems to be a 5370 USB chip based device, which is not supported
>>>> by any official Linux kernel yet.
>>>> There is support for 5390 PCI chip based devices added in the next upcoming
>>>> Linux kernel (2.6.39), but that still won't support the 5370 based devices
>>>> yet.
>>>>
>>>> From what our experience with Ralink devices is, is that the 5370 is not much
>>>> different from the 5390, so it probably won't be much work to have the rt2800usb
>>>> driver support it, but it is still work that needs to be done.
>>>
>>> So is it brand new? And if it is, do you have any clue on how it is
>>> different, better?. It is
>>> advertised as a T1R1 device, so I don't understand why they release
>>> another device
>>> that works like the 3070...
>>>
>>> Well, I'll see if I can invest some time on it...
>>
>> One idea would be to take the latest compat-wireless package and add the VID and PID
>> in there, and see what happens. Maybe it is just a matter of adding the correct USB
>> device IDs.
> 
> Tried it (but with compat from 13-03-2011) but it did not work,
>  the RF chipset version is unknown for the driver,
>  I will try it with the newest and other things, but not before next Wednesday.

Indeed, that version of compat-wireless should already provide support for RT5390.
In that case the debug logging of rt2x00 would be interesting, especially the line
indicating chipset information.

> 
>>
>>>
>>>>
>>>> Just out of curiosity, what brand of device is it?
>>>
>>> Hi Gertjan, thanks a lot for the very fast reply, I appreciate it.
>>>
>>> The device does not have any kind of brand on it, It came on a plastic container
>>> with a green cover and a very generic instruction booklet. The mini CD that came
>>> was burned (so no series production) and it contained the staging driver for the
>>> 5370 chipset (which is entirely useless for me as I won't use anything
>>> other than rt2x00)
>>>
>>> I guess it is some sort of generic OEM device, I'll see if I can get
>>> some more samples.
>>>
>>
>> OK. I hadn't seen any 5370 devices "in the wild" yet, so I was hoping it was a device
>> that I could get hold of myself as well, for testing and coding purposes.
> 
> If I get more, I'll send you one.

OK. Thanks.

> 
>>
>> ---
>> Gertjan
>>
> 


-- 
---
Gertjan