From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleksij Rempel Date: Tue, 09 Jul 2013 10:50:06 +0200 Subject: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA In-Reply-To: <51DBCE01.5030406@djardin.de> References: <51DA79B6.8030702@djardin.de> <51DBCE01.5030406@djardin.de> Message-ID: <51DBCEBE.7010405@rempel-privat.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org How replacing AP with about MESH or AdHock+BATMAN? Am 09.07.2013 10:46, schrieb David Jardin: > Hi Adrian, > > thanks for the response. That's bad news. > > I thought about using the Pi's as they have much more RAM and CPU power > than normal consumer access points have - which seems to be the limiting > factor of clients on those devices. And as we are a non profit > organization we simply can't afford business class access points (Cisco > etc.) as they are way to expensive. > > David > > Am 08.07.13 22:07, schrieb Adrian Chadd: >> The ath9k_htc stuff isn't ready to do what you want. And even if it >> was, the performance would be sub-par compared to the SoC designs. >> There's just not a lot of RAM on these things; even if we do >> eventually push almost everything into the driver instead of firmware, >> there's still only a limited amount of RAM for packet buffers. So >> you're never going to reach the same level of performance as >> direct-attach. >> >> I suggest you spend the money on some slightly more useful access >> points. You'll likely be able to serve at least 2x the clients on a >> single 2x2 tplink or dlink access point for about $50-$70 each. >> >> Good luck, >> >> >> -adrian >> (Why does everyone see "Raspberry pi" as the solution to everything >> these days? Sheesh..) >> >> >> On 8 July 2013 01:35, David Jardin wrote: >>> Hi, >>> -- Regards, Oleksij