On Mon, Feb 06, 2017 at 01:23:24AM +0300, Rostislav Devyatov wrote: > I want to decide what to include in my bug report (if I send one), I > am asking the following precise question: are the following parameters > intended to be manually included in the .config file of release 2.6? > All of them are present in the source files in the version 2.6 (latest > release) tree, I've checked it: > CONFIG_IBSS_RSN (I guess that the answer is yes, from the previous emails) Yes, this is described now and should be enabled as an option for normal production use cases. > CONFIG_BGSCAN_SIMPLE, CONFIG_BGSCAN_LEARN (I guess that the answer is > yes, from the previous emails) I'm adding these and this could be included as options for normal production use cases. > CONFIG_DRIVER_HOSTAP (and other CONFIG_DRIVER_* options listed in > src/drivers/drivers.c) This is not applicable for wpa_supplicant anymore, i.e., driver_hostap.c is only maintained for hostapd. > CONFIG_MESH (present in the defconfig of the current tree, but not in > the defconfig of 2.6) Yes, this is described now and should be enabled as an option for normal production use cases. > Also, the options the configuration script is trying to turn on depend > on the configuration of gentoo linux itself, the ones I mentioned come > from the default configuration, other configurations also try to turn > on: > > CONFIG_WPS_UPNP This is not really applicable for wpa_supplicant. The CONFIG_WPS_ER=y option enables this automatically to cover the build needs, but CONFIG_WPS_UPNP=y is internally only parameter for wpa_supplicant and only applicable as a build option for hostapd. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
