See the bugzilla reference below. Any objections? I can't
imagine that an AP would want to use the low resolution clock
since they aren't supposed to sleep anyway - and the HAL does
something similar...
When using the external sleep clock in AP mode, the
TSF increments too quickly, causing beac
On Tue, Dec 22, 2009 at 7:45 PM, Thiemo Nagel
wrote:
> One more thing: I'd like to emphasize that I had system freezes also hours
> after loading the ath5k module. Any idea whether that can be explained by
> the same bug?
Well it doesn't necessarily have to happen right after modprobe - any cal
Bob Copeland wrote:
>> - ath5k_hw_register_timeout() - which can spin for 1/3s (or more if
>> udelay is broken)
>
> Just one other thought - maybe udelay _is_ broken. You may try
> without using the HPET (CONFIG_HPET_TIMER=n).
I had another softlockup approx 2s after executing
rmmod ath5k; mo
> I should probably also switch to the packaging of hostapd John
> W. Linville is preparing for Fedora
> (https://bugzilla.redhat.com/show_bug.cgi?id=548180). Just in case I
> have made some kind of mistake in building it.
That helped! I've no idea what was wrong with my build of hostapd,
but up
On 22.12.2009 02:24 海藻敬之 wrote:
> Does original Atheros HAL calls the function just for 5GHz
> or calls for both 2GHz and 5 GHz.?
For both, too, the condition used is IS_CHAN_OFDM(chan).
> --- reset.c_org 2009-12-17 17:01:29.0 +0900
> +++ reset.c 2009-12-22 09:51:16.0 +0900
> @@ -6
