Kalle Valo wrote: > Sebastian Smolorz <Sebastian.Smolorz@xxxxxx> writes: > > Kalle Valo wrote: > >> I debugged this a long time ago. The problem is that firmware's > >> CMD_JOIN only works if bssid is correct one. I remember trying > >> ff:ff:ff:ff:ff:ff, but that didn't work for some reason. The join > >> command needs to be sent before association, otherwise transmission > >> won't work at all. And if I use a random bssid the firmware will > >> filter the replies. But I tested this a long time ago, I might > >> remember something wrong. > >> > >> I was thinking a hack which would get bssid from association frames > >> and then send CMD_JOIN, before the association frame. > > > > Could you elaborate a little bit on this? > > Basically my idea is this (all in tx path): > > 1. if tx frame is an association frame, get bssid from the frame > 2. if bssid == priv->bssid, goto step 6 > 3. store tx frame, don't transmit it yet > 4. send CMD_JOIN with new bssid > 5. wait for command completion > 6. priv->bssid = bssid > 7. transmit tx frame > 8. done > > Ugly as hell, but one option to get the driver working again. > > > How do we proceed to make the driver working again? Do you want to work > > on this issue? > > Sorry, currently I only have time to review patches and send comments. > If you have the time, it would be great to if you could fix the driver > finally. OK, I will write a patch. -- Sebastian -- 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
