[rt2x00-users] [PATCH] rt2x00: Export rt2x00soc_probe from rt2x00soc

[Helmut Schaa]

Removed John and linux-wireless
CC'ed users at rt2x00.serialmonkey.com

Am Mittwoch 03 März 2010 schrieb Gertjan van Wingerde:
> On Wed, Mar 3, 2010 at 6:04 PM, Helmut Schaa
> <helmut.schaa at googlemail.com> wrote:
> > Am Mittwoch 03 März 2010 schrieb Gertjan van Wingerde:
> >> Thanks for doing this. I couldn't test these configurations as I am
> >> lacking SoC devices.
> >
> > No problem, I'm just trying to get the driver up on one of these SoC devices.
> > Not sure how far I'll get :)
> >
> 
> All I can say is to please keep us informed on your progress. It is
> the first time I'm hearing someone actually working with a SoC device.
> 
> Can you share some information on what device you have,

The device is an Engenius AP based on a RaLink rt3050 SoC board. 

> and what
> Ralink chipset is on this device (the detection messages in dmesg for
> this device would be interesting).

After quite a bit of debugging/fixing I was able to get rt2800pci loaded
on the device without oopsing ;) (the patches I wrote are mainly _ugly_
hacks, so I need to clean them up first before posting).

At least here is the chip info:

phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 2872, rf: 0008, rev: 0200.

At least the rf value seems incorrect to me, 0008 = RF3022 which is (based on
the comments in rt2800.h) a 2.4G 2T2R but I'm pretty sure to have a 1T1R
device. I guess the eeprom data (read from flash) is just garbage because of
the hardcoded access address in rt2800pci.c.

Is there a way to determine if the eeprom data is correct? Any magic
numbers or the like?

Afterwards I was able to set the managed mode interface up with the
following in dmesg:

phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 3, CWmax: 4, Aifs: 2, TXop: 102.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 5, Aifs: 2, TXop: 188.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 3, TXop: 0.
phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 7, TXop: 0.

Nevertheless I wasn't able to get any scan results. Any ideas on how I can
debug that further? Could that be related to the eeprom mess?

Thanks,
Helmut