On Feb 4, 2008 8:39 PM, Felix Fietkau <nbd@xxxxxxxxxxx> wrote:
> Tomas Winkler wrote:
> > Will this work work you?
> >
> > ieee80211_tx_ratectrl {
> > u32 bitrate ( or pointer to ieee80211_rate I prefer no)
> > u32 flags
> > u32 retry_count
> > }
> >
> > ieee80211_tx_status {
> > ieee80211_tx_ratectrl retry_count[ X] / * X >= 4 */
> > }
> I guess that would work, but shouln't the array below be dynamic based on
> what the driver can do? Many drivers can only work with one or two rates, IMHO.
The problem that this structure is passed with each packett I don't
like the idea that anybody would even try to allocate and free this
structure as packets goes. However what about the following?
ieee80211_tx_status {
size_t nrates;
ieee80211_tx_ratectrl retry_count[0] ;
}
> - Felix
>
-
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
