From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA
Date: Fri, 22 Nov 2013 07:10:24 -0800 [thread overview]
Message-ID: <528F73E0.80903@candelatech.com> (raw)
In-Reply-To: <528F71ED.6000307@rempel-privat.de>
On 11/22/2013 07:02 AM, Oleksij Rempel wrote:
> Am 22.11.2013 16:00, schrieb Ben Greear:
>> On 11/22/2013 06:47 AM, Oleksij Rempel wrote:
>>> Am 22.11.2013 15:40, schrieb Ben Greear:
>>>> On 11/22/2013 02:23 AM, Oleksij Rempel wrote:
>>>>> Am 20.11.2013 20:01, schrieb Gustavo Azambuja:
>>>>>> Ben, thanks for you reply.
>>>>>> I need to convert my rPi into a AP (is not an option a "real" AP) to
>>>>>> get at less 30 stations. You know some way to get a list of
>>>>>> devices/drivers can support this?
>>>>>
>>>>> It's all about USB, RAM and power.
>>>>> If you use usb to communicate with wireless hardware, then your first
>>>>> problem is usb - it is too slow! Some times it is too slow even for one
>>>>> connection. This is why we have usb wifi adapters with internal cpu,
>>>>> ram
>>>>> and firmware (micro operation system). If you wont to add more
>>>>> connections you will need more ram and may be more cpu power. This will
>>>>> need more power from usb, which is limited to 500mA.
>>>>> In this case, just take some AP, connect it over ethernet and you will
>>>>> get same result.
>>>>
>>>> The RAM is certainly an issue, but just adding more stations should not
>>>> have much CPU impact as the total throughput is unlikely to increase
>>>> as more stations are added.
>>>>
>>>> Changing software to make better use of RAM is also unlikely to increase
>>>> power usage, though adding more RAM to the hardware might.
>>>
>>> patches are welcome
>>
>> I'm sure :)
>>
>> My customers are all interested in /AC these days, so I'm putting my
>> effort there. If/when someone opens an /AC firmware to the public
>> I will be all over it!
>
> AC?
>
>
802.11 ac, for instance ath10k.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-11-22 15:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 8:35 [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA David Jardin
2013-07-08 20:07 ` Adrian Chadd
2013-07-09 8:46 ` David Jardin
2013-07-09 8:50 ` Oleksij Rempel
2013-07-09 9:18 ` Felix Fietkau
2013-07-09 9:34 ` Oleksij Rempel
2013-07-09 9:52 ` Felix Fietkau
2013-07-09 11:23 ` Adrian Chadd
2013-11-20 18:44 ` Gustavo
2013-11-20 18:58 ` Ben Greear
2013-11-20 19:01 ` Gustavo Azambuja
2013-11-22 10:23 ` Oleksij Rempel
2013-11-22 14:40 ` Ben Greear
2013-11-22 14:47 ` Oleksij Rempel
2013-11-22 15:00 ` Ben Greear
2013-11-22 15:02 ` Oleksij Rempel
2013-11-22 15:10 ` Ben Greear [this message]
2013-11-25 10:52 ` Alex Hacker
2013-11-25 11:45 ` Sujith Manoharan
2013-11-25 12:02 ` Alex Hacker
2013-11-25 19:19 ` Adrian Chadd
2013-11-25 19:28 ` Ben Greear
2013-11-25 20:19 ` Adrian Chadd
2013-11-26 7:24 ` Alex Hacker
2013-11-26 8:18 ` Adrian Chadd
-- strict thread matches above, loose matches on Subject: below --
2013-11-22 15:33 Trevor Cullen
2013-11-23 1:35 ` Sujith Manoharan
2013-11-25 11:27 Trevor Cullen
2013-11-25 11:57 ` Alex Hacker
2013-11-25 11:41 Trevor Cullen
2013-11-25 11:41 ` Sujith Manoharan
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=528F73E0.80903@candelatech.com \
--to=greearb@candelatech.com \
--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