On Sat, Jan 24, 2009 at 3:12 AM, Alina Friedrichsen <x-alina@xxxxxxx> wrote:
> {
> ATH5K_TRACE(ah->ah_sc);
>
> - ath5k_hw_reg_write(ah, 0x00000000, AR5K_TSF_L32);
> - ath5k_hw_reg_write(ah, (tsf64 >> 32) & 0xffffffff, AR5K_TSF_U32);
> ath5k_hw_reg_write(ah, tsf64 & 0xffffffff, AR5K_TSF_L32);
> + ath5k_hw_reg_write(ah, (tsf64 >> 32) & 0xffffffff, AR5K_TSF_U32);
> }
Perhaps there is an internal latch on this pair; that may explain why
you need to write low->high order.
However, you don't need to write (tsf64 >> 32) & 0xffffffff; it's
unsigned so the mask is unnecessary.
--
Bob Copeland %% www.bobcopeland.com
--
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
