2011.11.09. 23:57 keltezéssel, Daniel Kuehn írta:
from: Daniel Kuehn dan...@kuehn.se
Most ath9k devices are PCI/PCIe based, therefor making PCI/PCIe support
default y helps those porting a config from 2.6 kernel series
from getting non-functional wireless drivers with 3.x kernel series.
On Thu, 17 Nov 2011 16:13:53 +0100
Gabor Juhos juh...@openwrt.org wrote:
2011.11.09. 23:57 keltezéssel, Daniel Kuehn írta:
from: Daniel Kuehn dan...@kuehn.se
Most ath9k devices are PCI/PCIe based, therefor making PCI/PCIe support
default y helps those porting a config from 2.6 kernel
2011.11.17. 16:39 keltezéssel, Daniel Kuehn írta:
I agree with you there if it was removed before, maybe then only the help
section of ath9k should be changed to say that you have to enable either
PCI/PCIe or AHB support for it to work?
Yes, adding a comment there would make sense, although
Hi Sangwook,
On 11/16/2011 01:34 PM, Sangwook Lee wrote:
On 15 November 2011 16:37, Kalle Valo kv...@adurom.com
mailto:kv...@adurom.com wrote:
Hi Sangwook,
On 11/15/2011 01:23 PM, Sangwook Lee wrote:
The patch series proposes to rename ath9k_platform.h to
On Thu, 17 Nov 2011 19:44:59 +0100
Gabor Juhos juh...@openwrt.org wrote:
2011.11.17. 16:39 keltezéssel, Daniel Kuehn írta:
I agree with you there if it was removed before, maybe then only the help
section of ath9k should be changed to say that you have to enable either
PCI/PCIe or AHB
hi,
I make an ioctl call with SIOCGIWPRIV and it fails.
I have included : #includelinux/wireless.h
The pcap code makes the same call to the driver in enter_rfmon_mode_wext()
defined in pcap-linux.c for sniffing.
The compat-wireless-2011-08-10 driver has the header file in
