>They are slow with our driver because the driver still lacks support for 11n >Tx >aggregation. Adding support for this is a non-trivial task.
Since you know what needs to be done and you have experience with coding efforts, could you please tell an estimation about how many people need to work on this full time and how much this may cost if someone is hired for the job? I see many complaints about various things in OpenBSD, but they are not tackled in the following manner: * how many people do want feature X? > how much does it costs? > do we get the money from donations for +this+ specific task/job? I don't say it should be done like this or like that. I am not even sure code will be accepted. I remember an action like that was conducted with pcc compiler i think , back in time then it was canceled. So, do users want wifi good support in OpenBSD badly enough to pay for it? Then trace some things needed to be done in network stack, evaluate costs and announce that. Some people may step in for the money. If not, wait for good samariteans to code all that and focus the money of attack surface reduction, etc. Simple as that. Next question on the list should be answered: 'NO, there is no wifi support in OpenBSD, just some work in progress'. I am already tired of wifi explanations going on over and over again on the list, because people do not search the list. >What's cool about USB athn though is that the firmware we use is open source. >In theory, anyone could fix anything in the firmware and driver. I remember a guy from openwrt telling anything Qualcomm related is closed and they are not able to provide any documentation since all is wrapped in legal contracts nobody wants to break. He said he thinks they will not be ever able to provide free docs because of lawyers.
