On Mon, Nov 01, 2010 at 05:55:48PM -0700, Brian Cavagnolo wrote: > From: Nishant Sarmukadam <nishants@xxxxxxxxxxx> > > AP firmware uses xmitcontrol to differentiate between AMPDU > and non-AMPDU frames. As the support for AMPDU is not yet > added, set xmitcontrol to non-AMPDU for all tx frames for AP > firmware. This field will be set to indicate ampdu/non-ampdu > frames when tx AMPDU support is added. > > Signed-off-by: Pradeep Nemavat <pnemavat@xxxxxxxxxxx> > Signed-off-by: Brian Cavagnolo <brian@xxxxxxxxxxx> It's still pretty dumb of the firmware to require that the driver tell the firmware _again_ (it already has that info) whether a TX packet is part of an AMPDU session or not, but I guess this requirement is set in stone now. I'm still not happy that it just does this blindly based on whether the image is an AP firmware image or not (earlier AP images did not require this). Ideally they'd just replace the firmware people by ones that have some taste, but that probably won't happen. Acked-by: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx> -- 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
