Christian Bremvåg 8f04e62ca7 Fix incorrect response to SIOCGIWESSID ... When not associated with an AP, wifi device drivers should respond to the SIOCGIWESSID ioctl with a zero-length string for the SSID, which is the behavior expected by dhcpcd. Currently, this driver returns an error code (-1) from the ioctl call, which causes dhcpcd to assume that the device is not a wireless interface and therefore it fails to work correctly with it thereafter. When not associated with an AP, other wifi device drivers respond to the SIOCGIWESSID ioctl with a zero-length string for the SSID; this is the behaviour expected by dhcpcd. This driver returns an error code (-1) from the ioctl call - this causes dhcpcd to assume that the device is not a wireless interface and therefore it fails to work correctly with it thereafter. It would be good if the behaviour of this driver could be brought into line with that of other drivers for similar devices; that is for the response to SIOCGIWESSID to be a zero-length string and a success code rather than an error.		2019-08-16 22:53:33 +02:00
..
custom_gpio_linux.c
ioctl_cfg80211.c	Upstream changed wireless band	2019-08-16 18:22:55 +02:00
ioctl_cfg80211.h
ioctl_linux.c	Fix incorrect response to SIOCGIWESSID	2019-08-16 22:53:33 +02:00
ioctl_mp.c
mlme_linux.c	Remove signal handling from driver (software)	2019-08-16 22:11:06 +02:00
os_intfs.c	Remove signal handling from driver (software)	2019-08-16 22:11:06 +02:00
recv_linux.c
rhashtable.c
rhashtable.h
rtw_android.c
rtw_cfgvendor.c
rtw_cfgvendor.h
rtw_proc.h
rtw_rhashtable.c
rtw_rhashtable.h
usb_intf.c	Pushing minor cleanups ..	2019-08-16 22:49:56 +02:00
usb_ops_linux.c
wifi_regd.c	Upstream changed wireless band	2019-08-16 18:22:55 +02:00
xmit_linux.c