On Sat, Oct 31, 2009 at 10:31 AM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote:
>
> The WMI event of type 0x100b received is an empty frame of 4 bytes.
>
> [ 1970.466441] ath9k_htc: unhandled wmi event id: 0x100b
> [ 1970.466452] 00 00 00 00 ....
This seems to be a WMI_NODE_TIMEOUT_EVENTID, the code I see that
handles this is:
static void hst_ath_node_update_timeout(struct ath_softc *sc,
a_uint8_t *pBuffer, a_uint32_t buf_len)
{
struct ieee80211_node *ni;
struct ieee80211_node_table *nt = &(sc->sc_ic.ic_sta);
WMI_NODE_TIMEOUT_EVENT *wmi_data = (WMI_NODE_TIMEOUT_EVENT *)pBuffer;
a_uint32_t can_reset = 0;
asf_tailq_foreach(ni, &nt->nt_node, ni_list) {
can_reset = wmi_data->nodetimeoutmask & (0x1 << ni->ni_nodeindex);
if (can_reset)
ni->ni_inact = ni->ni_inact_reload;
else
ni->ni_inact--;
}
}
So it seems the firmware triggers NODE_TIMEOUT_EVENTID events even if
we have no nodes (I take a node would be an AP if we're associated to
it).
What exactly is this for?
Luis
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
