Ok, let me be slightly clearer. There's a bunch of clocks that are derived in a hierarchy. For example, there's a AR_USEC, which has a bunch of "how many X in Y."
There's "how many clock cycles in 1 microsecond." However, since that's used _EVERYWHERE_ in the MAC for all the interframe spacings, I don't suggest you fondle that. You'll actively break specification that way. There's likely a similar register which sets how many ticks or microseconds in a TSF, but I'd have to go digging and I'm a bit busy at the moment, sorry. Adrian On 29 October 2012 10:08, Adrian Chadd <adr...@freebsd.org> wrote: > On 29 October 2012 03:20, Amin Gholoobi <amin.gholo...@gmail.com> wrote: > >> Normally a wireless reference clock is running at 1MHz and I would like to >> modify this one so it can run at 40MHz. >> >> I was wondering if there is any option in the driver which I can change and >> adjust the reference clock due to my needs. > > The TSF/TU counters are derived from an internal clock. You can't up > that clock by 40x to get a 40 times faster TSF/TU. :-) > > Thanks, > > > Adrian _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
