[rt2x00-users] Support for Ralink 5370 WiFi USB dongle

[Gertjan van Wingerde]

On 11/14/11 22:59, Gertjan van Wingerde wrote:
> On 11/10/11 00:41, Ingvar Hagelund wrote:
>> * Gertjan van Wingerde 
>>>>> So, the RF chipset if properly reported here.
>>>>>
>>>>> Also note that the RF chipset identification was not a guess, as this code was submitted by Ralink
>>>>> themselves.
>>>>>
>>>>> I seem to recall that you are running on a PPC32 platform, is that correct?
>>>>>
>>>>> Would it be possible for you to connect the device to an x86 based platform, to make sure that we
>>>>> aren't running in some strange BE related problem?
>>
>> * Ingvar Hagelund
>>> Built on a fedora 15 laptop running a 3.1.0 kernel from fedora 16 on x86_64. Driver seems to work well, and I get decent speed over WPA2, at least 12Mbps.
>>>
>>> This is with no patches, just latest compat-wireless. So this might mean that the problems I saw may have been related to the 32bit ppc arch specifically.
>>
>> So, this could be related to endianess. I'm willing to work with this
>> and do testing, though I'm not much of a coder. I had a look at the code
>> that does endian "decoding" when necessary, and it seems that those
>> parts were merged earlier this fall.
>>
>> So ... I'm a bit at a loss here. What should I do? I could try to remove
>> the endian bit-juggling here and there, and check if the RF chipset
>> changes, perhaps. Any other suggestions?
>>
> 
> Hi Ingvar,
> 
> Would you be able to apply the attached diagnostics patch and report back on the dmesg output at module loading time?
> 
> Hopefully this would allow us to get a bit closer to the cause of the issue.
> 

Woops, there seems to be a bug in the patch I sent. Please use the attached patch instead.

---
Gertjan
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: rt2x00_efuse_eeprom_read_dump.patch
URL: <http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/attachments/20111115/685bee5e/attachment.pl>