On 23 Mar 2010, at 13:23, Alexander Egorenkov wrote:
> We also need to set/update/delete these capabilities for nodes, e.g. after a
> beacon or
> a (re)association frame is received from a node. I mean the field ni_flags in
> struct ieee80211_node. And ifconfig support would be nice to have in
We also need to set/update/delete these capabilities for nodes, e.g. after a
beacon or
a (re)association frame is received from a node. I mean the field ni_flags
in struct ieee80211_node. And ifconfig support would be nice to have in
order to be able to enable/disable these features dynamically.
O
On 13 Mar 2010, at 16:17, Alexander Egorenkov wrote:
> I have finally patched net80211 on my system and added HT extended
> capabilities support.
>
> Here are the patches.
>
> I added a new variable to ieee80211com struct.
> It seems that only the lowest 16 bit of ic_htcaps are used, an altern
I have finally patched net80211 on my system and added HT extended
capabilities support.
Here are the patches.
I added a new variable to ieee80211com struct.
It seems that only the lowest 16 bit of ic_htcaps are used, an alternative
to a new variable would be to use the highest 16 bit of ic_htcap
On 11 Mar 2010, at 16:32, Alexander Egorenkov wrote:
There are already constants defined in iee80211.h.
E.g. IEEE80211_HTCAP_MCSFBACK_UNSOL.
But the problem is that e.g. IEEE80211_HTCAP_MCSFBACK_UNSOL is equal
to 0x0200
and the capabilty constant IEEE80211_HTCAP_RXSTBC_2STREAM has the
same
There are already constants defined in iee80211.h.
E.g. IEEE80211_HTCAP_MCSFBACK_UNSOL.
But the problem is that e.g. IEEE80211_HTCAP_MCSFBACK_UNSOL is equal to
0x0200
and the capabilty constant IEEE80211_HTCAP_RXSTBC_2STREAM has the same
value.
So we cannot use ic_htcap field for both capabilities
OK, here is an example.
There is no way to set MCS feedback capability in the filed hc_extcap of the
struct ieee80211_ie_htcap
because the function ieee80211_add_htcap_body always sets it to 0. And my
Ralink device supports MCS feedback
according to Linux device driver code. The same problem is wi
Alexander Egorenkov wrote:
Currently there is no possibility to set some HT capabilities in e.g. an
association request frame.
The function ieee80211_add_htcap_body in ieee80211_ht.c simply sets some HT
capabilities to zero.
For example, there is no way to set HT extended capabilities which i nee
Currently there is no possibility to set some HT capabilities in e.g. an
association request frame.
The function ieee80211_add_htcap_body in ieee80211_ht.c simply sets some HT
capabilities to zero.
For example, there is no way to set HT extended capabilities which i need
for my 802.11n device drive
