On Mon, 2007-10-15 at 16:34 +0900, bruno randolf wrote: > what do you think about the following solution? I don't like it. If we wanted to implement this in mac80211 we should do a zero-copy solution with pointers to header/data portion which is very hard right now because mac80211 has much assumptions that it's all contiguous. Secondly, this adds overhead for all hardware to mac80211 for something that can be *trivially* solved in the driver, and only a single driver so far requires it. I think the driver is a *much* better place to do this. > Atheros hardware requires the header to be padded to 4 byte (32 bit) > boundaries. It expects the payload data to start at multiples of 4 byte for TX > frames and will add the padding for received frames. For most headers there is > no need for padding, since they are multiples of 4 already - except QoS and 4 > address headers. > > This adds a new hw flag IEEE80211_HW_HEADER_PADDING to tell mac80211 that such > a padding is needed. [patch snipped] johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
