Re: [RFC] How to store HT (40MHz) support

2010-01-21 Thread Rafał Miłecki
W dniu 20 stycznia 2010 11:18 użytkownik Johannes Berg johan...@sipsolutions.net napisał: On Wed, 2010-01-20 at 01:06 +0100, Rafał Miłecki wrote: +             phy-use_40mhz = conf_is_ht(conf); This is wrong, conf_is_ht might also be 20mhz, look at the other helpers. I tried to understand

Re: [RFC] How to store HT (40MHz) support

2010-01-21 Thread Luis R. Rodriguez
2010/1/21 Rafał Miłecki zaj...@gmail.com: W dniu 20 stycznia 2010 11:18 użytkownik Johannes Berg johan...@sipsolutions.net napisał: On Wed, 2010-01-20 at 01:06 +0100, Rafał Miłecki wrote: +             phy-use_40mhz = conf_is_ht(conf); This is wrong, conf_is_ht might also be 20mhz, look at

Re: [RFC] How to store HT (40MHz) support

2010-01-20 Thread Johannes Berg
On Wed, 2010-01-20 at 01:06 +0100, Rafał Miłecki wrote: + if (phy-supports_40mhz) That is useless, if it doesn't support it then you should not advertise it and mac80211 will not use it. + phy-use_40mhz = conf_is_ht(conf); This is wrong, conf_is_ht might also be 20mhz, look

[RFC] How to store HT (40MHz) support

2010-01-19 Thread Rafał Miłecki
In N-PHY code we have to make some decisions based on fact if band is 40MHz. AFAIU when registering device, driver reports to mac80211 HT capability and this is not implemented yet. For that we will need to modify: static struct ieee80211_supported_band b43_band_5GHz_nphy = { ... } Then