I’m afraid you are right
I have the following modules running
ath9k_htc 85879 0
ath9k_common 13619 1 ath9k_htc
ath9k_hw 429197 2 ath9k_common,ath9k_htc
ath19187 3 ath9k_common,ath9k_htc,ath9k_hw
mac80211 513247 2 rtl8187,ath
Am 08.07.2014 13:37, schrieb Janusz Dziedzic:
> On 8 July 2014 08:20, Hosam Hittini wrote:
>> Hello there,
>>
>> I have this dual band wireless adapter
>> https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-dual-band-usb-adapter-gnu-linux-tpe-nusbdb
>> and it uses AR9280 chipset for the 5GHz
On 8 July 2014 08:20, Hosam Hittini wrote:
> Hello there,
>
> I have this dual band wireless adapter
> https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-dual-band-usb-adapter-gnu-linux-tpe-nusbdb
> and it uses AR9280 chipset for the 5GHz communication
> It’s using ath9k driver; I have Ubun
Am 08.07.2014 09:48, schrieb Hosam Hittini:
> Is it a driver limitation or a firmware limitation?
> Because in theory, configuring the AP on the two bands is not different
> at all
It is suggestion provided by EEPROM, so driver is free to fallow it. If
you will force the driver not to fallow it, a
Is it a driver limitation or a firmware limitation?
Because in theory, configuring the AP on the two bands is not different at all
Regards,
Eng. Hosam Hittini
On Jul 8, 2014, at 11:35 AM, Oleksij Rempel wrote:
> Am 08.07.2014 08:20, schrieb Hosam Hittini:
>> Hello there,
>>
>> I have this dual
Am 08.07.2014 08:20, schrieb Hosam Hittini:
> Hello there,
>
> I have this dual band wireless
> adapter
> https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-dual-band-usb-adapter-gnu-linux-tpe-nusbdb
> and it uses AR9280 chipset for the 5GHz communication
> It’s using ath9k driver; I have
