On Sat, Oct 17, 2009 at 22:18, Bartlomiej Zolnierkiewicz <bzolnier@xxxxxxxxx> wrote: > On Saturday 17 October 2009 16:54:03 Bartlomiej Zolnierkiewicz wrote: >> >> [ I somehow missed this one by not being on cc: ] >> >> On Thursday 15 October 2009 22:04:14 Ivo van Doorn wrote: >> > Add support for the rt2860/rt3090 chipsets from Ralink. >> > >> > Includes various patches from a lot of people who helped >> > getting this driver into the current shape. >> > >> > Signed-off-by: Alban Browaeys <prahal@xxxxxxxxx> >> > Signed-off-by: Benoit PAPILLAULT <benoit.papillault@xxxxxxx> >> > Signed-off-by: Felix Fietkau <nbd@xxxxxxxxxxx> >> > Signed-off-by: Luis Correia <luis.f.correia@xxxxxxxxx> >> > Signed-off-by: Mattias Nissler <mattias.nissler@xxxxxx> >> > Signed-off-by: Mark Asselstine <asselsm@xxxxxxxxx> >> > Signed-off-by: Xose Vazquez Perez <xose.vazquez@xxxxxxxxx> >> > Signed-off-by: Ivo van Doorn <IvDoorn@xxxxxxxxx> >> > --- >> > http://kernel.org/pub/linux/kernel/people/ivd/patches/0003-rt2x00-Implement-support-for-rt2800pci.patch >> >> First let me say that I'm very happy to see this patch finally being >> submitted and I appreciate the effort.. >> >> (I'll give it a spin on Eee 901 w/ 2.6.32-rc5 sometime later..) > > Unfortunately still no luck with it, works just like it worked when I first > tried it half a year ago (loads OK but "iwlist wlan0 scan" doesn't bring any > results).. > > Could somebody with the genuine RT2860 revision of the chip try the driver > and confirm that it works w/ 2.6.32-rc5 so I will know whether I should be > looking for some generic problem or RT2880 revision specific one? With my RaLink RT2760 Wireless 802.11n 1T/2R Cardbus [1814:0701], it fails right after loading the firmware to the card. (this is an internal PCI card, not cardbus) Oct 16 23:08:15 lc kernel: phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 0701, rf: 0003, rev: 28600102. Oct 16 23:08:23 lc kernel: phy0 -> rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'. Oct 16 23:08:23 lc kernel: phy0 -> rt2x00lib_request_firmware: Info - Firmware detected - version: 0.11. Oct 16 23:08:23 lc kernel: phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff Oct 16 23:08:23 lc kernel: phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff Oct 16 23:08:23 lc kernel: phy0 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xffffffff Oct 16 23:08:23 lc kernel: phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 3, CWmax: 4, Aifs: 2, TXop: 102. Oct 16 23:08:23 lc kernel: phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 5, Aifs: 2, TXop: 188. Oct 16 23:08:23 lc kernel: phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 3, TXop: 0. Oct 16 23:08:23 lc kernel: phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 7, TXop: 0. We get those "regbusy errors" and then, the MCU no longer accepts any command. Oddly though, it can scan and detect the surrounding AP's. Luis Correia, rt2x0 project admin -- 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
