Bruno Randolf <br1@xxxxxxxxxxx> writes: > On 10/22/2015 02:42 PM, Jes Sorensen wrote: >> Making things work against random kernel versions of OpenWRT is not >> particularly "credible". If the driver needs hacks to work with older >> kernels, then they should be applied for the older kernels. Linux does >> not have a history of carrying hacks in current drivers to accommodate >> older kernels. > > Well forget OpenWRT. The point is that this is not a hack - it's the > behavior that mac80211 expects and documents and moreover it does NOT > pass more data frames than before. > > It does not pass more data frames before association because the RCR > RCR_ACCEPT_AP bit is not set and the RCR_CHECK_BSSID_* bits are set. I have gone back and looked more at the vendor drivers over this issue. Most versions of the vendor driver consistently mess with both FLTMAP* and RCR, and disable packets when they go into a non-assoc state, but non-assoc to the vendor driver also means non-AP, non-monitor, etc. I really would like to know more about the difference between RCR and FLTMAP registers - Larry is there a chance you could try and ping your Realtek contacts about this? For now I have applied your patch and pushed it into both branches. Cheers, Jes -- 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
