Hi Johannes,
> Also, you have a ton of debugfs file API. Are you sure that's a good
> thing? Is it all really for debugging only? Also things like
> "passphrase" there make me very suspicious about what the driver is
> doing there. There doesn't seem to be any reason at all to provide an
> interface for a passphrase?
The following 5 APIs are for debugging purpose.
'info', 'debug', 'getlog', 'regrdwr', 'rdeeprom'
All other APIs (listed below) are for driver configurations.
mpactl, antcfg, passphrase, esuppmode
addbapara, txaggrprio, addbareject, txbufcfg, amsduaggrctrl,
txratecfg, httxcfg, htcapinfo,
atimwindow, deepsleep, hscfg, qoscfg, sleeppd
We will remove those APIs, including the APIs to achieve the highest throughput (e.g., the one that sets 40MHz channel width). All default settings will be used internally.
I have a question regarding the 11n 20MHz/40MHz channel width configuration:
Since the 802.11n Draft 2.0 System Interoperability Test Plan v1.1 requires the default configuration being set to 20MHz, is there any way to set the channel width to 40MHz at run-time?
Thanks for your help,
Bing
ÿô.nlj·Ÿ®‰†+%ŠË±é¥Šwÿº{.nlj·¥Š{±ÿ«zW¬³ø¡Ü}©ž²ÆzÚj:+v‰¨þø®w¥þŠàÞ¨è&¢)ß«a¶Úÿûz¹ÞúŽŠÝjÿŠwèf
