"Gordon, Charles" <Charles.Gordon@xxxxxxxx> writes: > I'm writing a wireless driver that will use the mac80211 API. My > hardware = allows me to send one packet at a time. The driver is > suppose to set the t= x field (among others) in the struct > ieee80211_ops argument passed to ieee8= 0211_alloc_hw(). The tx field > should be loaded with a pointer to a low lev= el transmit routine. > However, it's not clear from the documentation if thi= s routine > should maintain a packet queue or not. Is it okay for the low le= vel > transmit routine to only allow one packet to be transmitted at a time, > = or should it maintain a queue of tx packets? It seems like the > mac80211 AP= I is already maintaining a queue, so I'm not sure that > the low level driver= should maintain a second one. In my opinion, the driver should not have a second queue. Just stop queue while transmitting the frame and wake the queue after it has been transmitted. -- Kalle Valo -- 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
