From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9280 AP mode - 5GHz band
Date: Tue, 08 Jul 2014 09:55:02 +0200 [thread overview]
Message-ID: <53BBA3D6.2020702@rempel-privat.de> (raw)
In-Reply-To: <828B04EB-D48B-4C8C-858C-698D18838ACC@gmail.com>
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, and it will damage your
hardware or produce some interference with radar working on 5GHz - it
will be your own responsibility.
Normally 5 GHz AP should provide Dynamic Channel Switch and Radar
Detection, which is not provided by ath9k_htc driver.
> Regards,
> Eng. Hosam Hittini
>
> On Jul 8, 2014, at 11:35 AM, Oleksij Rempel <linux@rempel-privat.de
> <mailto:linux@rempel-privat.de>> wrote:
>
>> 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 Ubuntu 13.10 running 3.11 kernel and the
>>> adapter worked out of the box
>>> I?m using hostapd to configure the adapter as a software AP
>>> When I tried to configure the adapter as an AP on the 2.4GHz channels it
>>> worked fine
>>> When tried the 5GHz channels it gives me the following error
>>>> channel [1] (40) is disabled for use in AP mode, flags: 0x77
>>>> wlan1: IEEE 802.11 Configured channel (40) not found from the channel
>>>> list of current mode (2) IEEE 802.11a
>>>> wlan1: IEEE 802.11 Hardware does not support configured channel
>>> In addition, _/*iw list*/_ command shows that the 5GHz channels have the
>>> ?passive scanning? and ?no IBSS? flags
>>> I can associate with an AP on the 5GHz though
>>> How to solve that
>>> Thank you
>>
>> 5GHz AP is not supported on this HW.
>>
>> --
>> Regards,
>> Oleksij
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org <mailto:ath9k-devel@lists.ath9k.org>
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
--
Regards,
Oleksij
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 278 bytes
Desc: OpenPGP digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140708/6814d4b7/attachment.pgp
next prev parent reply other threads:[~2014-07-08 7:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 6:20 [ath9k-devel] AR9280 AP mode - 5GHz band Hosam Hittini
2014-07-08 7:35 ` Oleksij Rempel
2014-07-08 7:48 ` Hosam Hittini
2014-07-08 7:55 ` Oleksij Rempel [this message]
2014-07-08 11:37 ` Janusz Dziedzic
2014-07-09 4:41 ` Oleksij Rempel
2014-07-09 5:47 ` Hosam Hittini
2014-07-09 8:50 ` Oleksij Rempel
2014-07-09 9:01 ` Hosam Hittini
2014-07-11 22:21 ` Hosam Hittini
2014-07-15 6:33 ` Oleksij Rempel
2014-07-22 12:38 ` Hosam Hittini
2014-07-22 15:56 ` Oleksij Rempel
2014-07-14 7:07 ` Hosam Hittini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53BBA3D6.2020702@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox