On Wed, Jun 10, 2009 at 10:28:25PM +0300, Jouni Malinen wrote: > I don't like the idea of making hostapd warn the user somehow, but could > probably live with something like AP mode being implemented in the > driver, but disabled by default. Only if the user were to use a module > parameter, say, broken_ap_mode=1, would the support for AP mode be > registered. As long as distros do not start adding this parameter by > default, this would force the user to become at least somehow informed > about the issues and make a conscious choice in enabling the mode. I would probably lean the other way -- let the driver expose the fact that his AP mode is dysfunctional, and require hostap to say it is OK to use it. Then again, it is the kind of thing that a user will say "OK" and then go on to file bug reports about the problems created by broken AP mode drivers... Like I said, "on the fence"... :-) John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
