[ath9k-devel] [PATCH 1/2] ath9k_htc: do some initial hardware configuration

2013-07-09 Thread Oleksij Rempel
Currently we configure harwdare and clock, only after interface start. In this case, if we reload module or reboot PC without configuring adapter, firmware will freeze. There is no software way to reset adpter. This patch add initial configuration and set it in disabled state, to avoid this freeze

[ath9k-devel] [PATCH 2/2] ath9k_htc: reboot firmware if it was loaded

2013-07-09 Thread Oleksij Rempel
Currently ath9k_htc will reboot firmware only if interface was ever started. Which lead to the problem in case where interface was never started but module need to be reloaded. This patch will partially fix bug "ath9k_htc: Target is unresponsive" https://github.com/qca/open-ath9k-htc-firmware/issu

Re: [ath9k-devel] ath9k_htc: Firmware - htc_9271.fw download failed

2013-07-09 Thread Oleksij Rempel
Hi Bo, Am 10.07.2013 04:24, schrieb Bo Shi: > Hi Oleksij, > The issue has gone after patch this. thank you very very much. Great! Thank you for testing. Please write some feedback on github: https://github.com/qca/open-ath9k-htc-firmware/issues/1 or to the mailing list > |--- a/drivers/net

Re: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA

2013-07-09 Thread Adrian Chadd
The newer, higher end tplink/dlink devices that use AR9344 ship with 128mb RAM and a 500MHz mips74k core. I think that's enough for your needs. -adrian On 9 July 2013 01:46, David Jardin wrote: > Hi Adrian, > > thanks for the response. That's bad news. > > I thought about using the Pi's as th

Re: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA

2013-07-09 Thread Felix Fietkau
On 2013-07-09 11:34 AM, Oleksij Rempel wrote: > Am 09.07.2013 11:18, schrieb Felix Fietkau: >> On 2013-07-09 10:50 AM, Oleksij Rempel wrote: >>> How replacing AP with about MESH or AdHock+BATMAN? >> Why? That sounds like a recipe for disaster to me (at least for >> conference networks). The ath9k_h

Re: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA

2013-07-09 Thread Oleksij Rempel
Am 09.07.2013 11:18, schrieb Felix Fietkau: > On 2013-07-09 10:50 AM, Oleksij Rempel wrote: >> How replacing AP with about MESH or AdHock+BATMAN? > Why? That sounds like a recipe for disaster to me (at least for > conference networks). The ath9k_htc stuff can't handle more peers in > mesh/ad-hoc th

Re: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA

2013-07-09 Thread Felix Fietkau
On 2013-07-09 10:50 AM, Oleksij Rempel wrote: > How replacing AP with about MESH or AdHock+BATMAN? Why? That sounds like a recipe for disaster to me (at least for conference networks). The ath9k_htc stuff can't handle more peers in mesh/ad-hoc than clients in AP mode. In setting up a conference net

Re: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA

2013-07-09 Thread Oleksij Rempel
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 lim

Re: [ath9k-devel] AP Limitation because of ATH9K_HTC_MAX_STA

2013-07-09 Thread 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

Re: [ath9k-devel] AR9580/90

2013-07-09 Thread Matthias May
On 08/07/13 15:29, Daniel Wunderlich wrote: > Hi all, > > could anyone provide the iw list output of an AR9580 oder AR9590 chipset? > > Thanks in advance, Daniel > > ___ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/ma