rt2500pci: regression with latest changes.

a-slack · **Posted:** Sat Jul 17, 2010 3:51 am

The patch rt2x00: Write the BSSID to register when interface is added:

Code:

--- a/drivers/net/wireless/rt2x00/rt2x00mac.c
+++ b/drivers/net/wireless/rt2x00/rt2x00mac.c
@@ -282,7 +282,8 @@ int rt2x00mac_add_interface(struct ieee80211_hw *hw,
     * has been initialized. Otherwise the device can reset
     * the MAC registers.
     */
-   rt2x00lib_config_intf(rt2x00dev, intf, vif->type, intf->mac, NULL);
+   rt2x00lib_config_intf(rt2x00dev, intf, vif->type,
+               intf->mac, intf->bssid);
 
    /*
     * Some filters depend on the current working mode. We can force

generates malfunction in managed mode with the rt2500pci driver, with that patch the device associates randomly.

Reverting that patch makes all work fine again.

Regards.

IvD · **Posted:** Sat Jul 17, 2010 10:19 am

Could you try attached patch to see if that fixed the problem for you?

a-slack · **Posted:** Sat Jul 17, 2010 4:58 pm

Yes, with that patch works

. I tried with compat-wireless-2010-07-16.tar.bz2 with no changes on it and it doesn't works then I tried the same tarball with your patch and it works well.

Regards.

a-slack · **Posted:** Sun Jul 18, 2010 8:37 pm

Sorry but after more tests with the patch bssid.diff happens the same, the device associates randomly (most of the times doesn't associate).

The unique thing that really works is revert the patch rt2x00: Write the BSSID to register when interface is added.

Regards.

IvD · **Posted:** Mon Jul 19, 2010 9:46 am

Could you try this new patch instead?

a-slack · **Posted:** Mon Jul 19, 2010 5:38 pm

The second one, after a few tests, seems to work well.

Regards.

rt2x00.serialmonkey.com

rt2500pci: regression with latest changes.

Who is online