* ath5k bf=xxx bf_skb=0 warnings
@ 2008-02-26 3:37 Krzysztof Halasa
2008-02-26 6:11 ` bruno randolf
0 siblings, 1 reply; 3+ messages in thread
From: Krzysztof Halasa @ 2008-02-26 3:37 UTC (permalink / raw)
To: linux-wireless
Hi,
Just wondering if "bf=xxx bf_skb=0" warnings printed to console
(ath5k/base.c:ath5k_beacon_send) are normal?
Linux ixp425 2.6.25-rc3 (ARM big-endian), AR5413
iwconfig wlan0 essid $ESSID mode ad-hoc channel $CH
iwconfig wlan0 key restricted $KEY
ifconfig wlan0 up
I understand sc->bbuf->skb is never set, the only possible place is
ath5k_beacon_update() but it's never called.
--
Krzysztof Halasa
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: ath5k bf=xxx bf_skb=0 warnings
2008-02-26 3:37 ath5k bf=xxx bf_skb=0 warnings Krzysztof Halasa
@ 2008-02-26 6:11 ` bruno randolf
2008-02-26 13:32 ` Krzysztof Halasa
0 siblings, 1 reply; 3+ messages in thread
From: bruno randolf @ 2008-02-26 6:11 UTC (permalink / raw)
To: Krzysztof Halasa; +Cc: linux-wireless
On Tuesday 26 February 2008 12:37:21 Krzysztof Halasa wrote:
> Hi,
>
> Just wondering if "bf=xxx bf_skb=0" warnings printed to console
> (ath5k/base.c:ath5k_beacon_send) are normal?
>
> Linux ixp425 2.6.25-rc3 (ARM big-endian), AR5413
>
> iwconfig wlan0 essid $ESSID mode ad-hoc channel $CH
> iwconfig wlan0 key restricted $KEY
> ifconfig wlan0 up
>
> I understand sc->bbuf->skb is never set, the only possible place is
> ath5k_beacon_update() but it's never called.
yes, that's normal and harmless. i haven't got around to make a smarter
solution yet.
that's because we call ath5k_beacon_config() each time after a channel is set
or the chip is reset, even if the beacon has not been configured yet.
we should fix that at some point.
bruno
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: ath5k bf=xxx bf_skb=0 warnings
2008-02-26 6:11 ` bruno randolf
@ 2008-02-26 13:32 ` Krzysztof Halasa
0 siblings, 0 replies; 3+ messages in thread
From: Krzysztof Halasa @ 2008-02-26 13:32 UTC (permalink / raw)
To: bruno randolf; +Cc: linux-wireless
bruno randolf <bruno@thinktube.com> writes:
> yes, that's normal and harmless. i haven't got around to make a smarter
> solution yet.
>
> that's because we call ath5k_beacon_config() each time after a channel is set
> or the chip is reset, even if the beacon has not been configured yet.
I see, thanks.
--
Krzysztof Halasa
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-02-26 13:32 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-26 3:37 ath5k bf=xxx bf_skb=0 warnings Krzysztof Halasa
2008-02-26 6:11 ` bruno randolf
2008-02-26 13:32 ` Krzysztof Halasa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).