From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sven Eckelmann <sven@open-mesh.com>
Cc: Kalle Valo <kvalo@adurom.com>,
OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
Simon Wunderlich <simon@open-mesh.com>,
ath10k@lists.infradead.org, Matti Laakso <malaakso@elisanet.fi>
Subject: Re: [OpenWrt-Devel] [PATCHv3] wifi: Introduce 802.11ac support
Date: Wed, 19 Feb 2014 11:41:35 +0200 [thread overview]
Message-ID: <87fvnfzbg0.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2862175.0bPvy6dDPg@bentobox> (Sven Eckelmann's message of "Mon, 17 Feb 2014 15:22:53 +0100")
(Adding ath10k@lists.infradead.org)
Sven Eckelmann <sven@open-mesh.com> writes:
> On Monday 17 February 2014 05:57:25 Kalle Valo wrote:
>> Sven Eckelmann <sven@open-mesh.com> writes:
>> > The ath10k patch wasn't resent because the driver patches are now
>> > integrated in the OpenWrt mac80211 package. The answer in
>> >
>> > http://article.gmane.org/gmane.comp.embedded.openwrt.devel/22422 also
>> > wasn't>
>> > quite promising.
>>
>> What do you mean? What was wrong with my answer?
>
> Nothing is "wrong" but you said that there are two branches. One is "AP mode,
> nothing else" and the other one is "main branch again has more
> features, like P2P, ...". So I don't see a good reason why a multi-purpose
> system like openwrt should accept my patch to change it to the "AP-only"
> ath10k firmware.
AP mode in 10.1 firmware is extensively tested and that's why I strongly
recommend to use 10.1 firmware as the default in openwrt. I don't think
it's wise to knowingle cripple ath10k AP mode in openwrt just because
lack of P2P support. Like Matti also said, AP mode is most important in
openwrt, we should have that properly supported first.
But we should try ways to mitigate the problem of having two firmware
branches. For example, should we have a module parameter in ath10k to
choose which firmware to use? Or is there even a way to do that
automatically based on what interfaces are used?
I'm happy to hear any ideas how to improve this.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next parent reply other threads:[~2014-02-19 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1391185897-29339-1-git-send-email-sven@open-mesh.com>
[not found] ` <87bny5lu4a.fsf@purkki.adurom.net>
[not found] ` <2862175.0bPvy6dDPg@bentobox>
2014-02-19 9:41 ` Kalle Valo [this message]
2014-02-19 11:22 ` [OpenWrt-Devel] [PATCHv3] wifi: Introduce 802.11ac support Jonas Gorski
2014-02-19 18:00 ` Ben Greear
[not found] ` <DUB122-W428FBB95DD2338614F9EB5CB990@phx.gbl>
2014-02-19 9:47 ` Kalle Valo
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=87fvnfzbg0.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@adurom.com \
--cc=malaakso@elisanet.fi \
--cc=openwrt-devel@lists.openwrt.org \
--cc=simon@open-mesh.com \
--cc=sven@open-mesh.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.