> > This is assuming that we don't manage to process the frame within 192 > > usecs. I guess that will be true since we defer it to a tasklet, but do > > we want to bet on it in the future or should we simply widen the window > > where the merge *won't* happen because the driver doesn't provide enough > > info and also add the 24 bytes offset here? > > sorry, i was to fast in agreeing ;) > on a second thought i realized that we don't need to worry about that: > > since we get to handle the frame after it was received *completely*, we can > be > sure that the current time returned by get_tsf() is later than the time when > byte 24 was received. so no need for adding the offset.
Hah, good point. johannes
signature.asc
Description: This is a digitally signed message part
_______________________________________________ ath5k-devel mailing list [email protected] https://lists.ath5k.org/mailman/listinfo/ath5k-devel
