If so, it's the same card as in the ASUS EEE PC and there's probably an OpenBSD howto somewhere. (I know there's one for FreeBSD.)

We are getting off subject here, but OpenBSD doesn't support the Eee PC's wireless Atheros chip yet partially because OpenBSD doesn't allow third party drivers. Otherwise, I've been running -current on mine for about a month now with no issue.

The shortest answer is that you can read/search the archives of the official misc@ mailing list as this is where developers answer some questions.

However, be aware that there are vast cultural differences between the OpenBSD community & what you may be more accustomed to in the Linux world. In the OpenBSD universe, the developers create, tweak, & enhance the operating system for themselves. Users have no say in what features are added & when those features are added unless they contribute code for consideration or fork out money. Even then, there is no guarantee that code contributions will be incorporated if the developers do not feel that the quality is high enough, stable enough, encumbered by license issues, or is not in line with the project's goals.

Drivers are announced & integrated into the operating system when they are ready. No sooner. Be aware that most wireless chipset vendors fear releasing specifications either to expose flaws or give intellectual property to their competitors. The OpenBSD project functions on open standards & specifications. This runs counter to what vendors want to make available, so it is not uncommon that the integration of drivers is slower here as opposed to other Open Source projects. If support is so critically important to you, the goals of the OpenBSD project may not be aligned with what you want.

If you decide to ask on misc@, be prepared to either be ignored, or blatantly told to go away. Attempting to apply pressure will simply be counter-productive.

Yes, I saw your post. To be blunt, I don't expect you will get a response for the reasons already discussed.

Although there is some virtue in persistence, both the number & frequency of your messages gives the appearance that you want & expect an immediate solution. Most likely, you will need to reset your expectations to something more realistic.

Given the closed nature of OpenBSD for both stability & security reasons, hacking solutions found in other operating systems to work with OpenBSD is not going to happen. Driver improvements will happen in due time. If you expect & want something to happen sooner, I respectfully suggest that you consider other operating systems.