From: Krishna Chaitanya <chaitanya.mgit@gmail.com> To: Ben Greear <greearb@candelatech.com> Cc: "Valo, Kalle" <kvalo@qca.qualcomm.com>, Johannes Berg <johannes@sipsolutions.net>, "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org> Subject: Re: [PATCH v2] ath10k: remove VHT capabilities from 2.4GHz Date: Wed, 27 Apr 2016 12:13:46 +0530 [thread overview] Message-ID: <CABPxzY+UuCABUcFbV0EpdoRaSzpgGvMani_j7xvg2a=xh-Bw0g@mail.gmail.com> (raw) In-Reply-To: <571FCB22.5000305@candelatech.com> On Wed, Apr 27, 2016 at 1:40 AM, Ben Greear <greearb@candelatech.com> wrote: > On 04/26/2016 01:07 PM, Krishna Chaitanya wrote: >> >> On Tue, Apr 26, 2016 at 5:33 PM, Valo, Kalle <kvalo@qca.qualcomm.com> >> wrote: >>> >>> Johannes Berg <johannes@sipsolutions.net> writes: >>> >>>> On Thu, 2016-04-21 at 08:15 -0700, Ben Greear wrote: >>>> >>>>> The thing is, it actually works just fine with the patch I posted >>>>> to fix mac80211, and at any rate, even if the mac80211 patch isn't >>>>> applied, the ath10k driver works just fine in HT mode. >>>> >>>> >>>> This patch has no implications on HT, and I wasn't planning on applying >>>> the mac80211 patch. >>> >>> >>> Yeah, makes sense. I'm planning to apply this soon. >>> >>>> As I said, I have no objections to doing the (Broadcom) vendor specific >>>> IEs for "VHT" in 2.4 GHz band, but I don't think we should advertise >>>> the spec IEs when they're explicitly specified to be used only in the >>>> 5.2 GHz band. >>> >>> >>> But we really should have this, any volunteers? :) I think it shouldn't >>> be too hard to do so this would be a good project for someone looking >>> for a simple, but useful, task on wireless stack. >> >> Are these Broadcom IEs documented somewhere? If yes, >> then its a matter of parsing them and adding support to >> minstrel_ht, isn't it? major work would be in minstrel. >> > > For ath10k, rate-ctrl is done in the firmware, so > no work at all in minstrel-ht. Right, i think this might become more common. So may we need to change minstrel_ht as well? > The end result, as far as I can tell, > is you would just have to tell mac80211 to allow > VHT on 2.4Ghz, and revert this patch that Kalle is proposing. Ideally as this is vendor specific it makes sense to implement this at Driver/FW level rather than implementing it at a common stack like mac80211. > Maybe someone that actually knows about these IEs can explain why > they are worth using? These IE's can be parsed in the driver without any mac80211 involvement.
WARNING: multiple messages have this Message-ID (diff)
From: Krishna Chaitanya <chaitanya.mgit@gmail.com> To: Ben Greear <greearb@candelatech.com> Cc: "Valo, Kalle" <kvalo@qca.qualcomm.com>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>, Johannes Berg <johannes@sipsolutions.net>, "ath10k@lists.infradead.org" <ath10k@lists.infradead.org> Subject: Re: [PATCH v2] ath10k: remove VHT capabilities from 2.4GHz Date: Wed, 27 Apr 2016 12:13:46 +0530 [thread overview] Message-ID: <CABPxzY+UuCABUcFbV0EpdoRaSzpgGvMani_j7xvg2a=xh-Bw0g@mail.gmail.com> (raw) In-Reply-To: <571FCB22.5000305@candelatech.com> On Wed, Apr 27, 2016 at 1:40 AM, Ben Greear <greearb@candelatech.com> wrote: > On 04/26/2016 01:07 PM, Krishna Chaitanya wrote: >> >> On Tue, Apr 26, 2016 at 5:33 PM, Valo, Kalle <kvalo@qca.qualcomm.com> >> wrote: >>> >>> Johannes Berg <johannes@sipsolutions.net> writes: >>> >>>> On Thu, 2016-04-21 at 08:15 -0700, Ben Greear wrote: >>>> >>>>> The thing is, it actually works just fine with the patch I posted >>>>> to fix mac80211, and at any rate, even if the mac80211 patch isn't >>>>> applied, the ath10k driver works just fine in HT mode. >>>> >>>> >>>> This patch has no implications on HT, and I wasn't planning on applying >>>> the mac80211 patch. >>> >>> >>> Yeah, makes sense. I'm planning to apply this soon. >>> >>>> As I said, I have no objections to doing the (Broadcom) vendor specific >>>> IEs for "VHT" in 2.4 GHz band, but I don't think we should advertise >>>> the spec IEs when they're explicitly specified to be used only in the >>>> 5.2 GHz band. >>> >>> >>> But we really should have this, any volunteers? :) I think it shouldn't >>> be too hard to do so this would be a good project for someone looking >>> for a simple, but useful, task on wireless stack. >> >> Are these Broadcom IEs documented somewhere? If yes, >> then its a matter of parsing them and adding support to >> minstrel_ht, isn't it? major work would be in minstrel. >> > > For ath10k, rate-ctrl is done in the firmware, so > no work at all in minstrel-ht. Right, i think this might become more common. So may we need to change minstrel_ht as well? > The end result, as far as I can tell, > is you would just have to tell mac80211 to allow > VHT on 2.4Ghz, and revert this patch that Kalle is proposing. Ideally as this is vendor specific it makes sense to implement this at Driver/FW level rather than implementing it at a common stack like mac80211. > Maybe someone that actually knows about these IEs can explain why > they are worth using? These IE's can be parsed in the driver without any mac80211 involvement. _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-04-27 6:44 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-21 13:17 [PATCH v2] ath10k: remove VHT capabilities from 2.4GHz Kalle Valo 2016-04-21 13:17 ` Kalle Valo 2016-04-21 15:15 ` Ben Greear 2016-04-21 15:15 ` Ben Greear 2016-04-21 20:09 ` Sebastian Gottschall 2016-04-21 23:07 ` Michael Ney 2016-04-26 7:04 ` Johannes Berg 2016-04-26 7:04 ` Johannes Berg 2016-04-26 12:03 ` Valo, Kalle 2016-04-26 12:03 ` Valo, Kalle 2016-04-26 20:07 ` Krishna Chaitanya 2016-04-26 20:07 ` Krishna Chaitanya 2016-04-26 20:10 ` Ben Greear 2016-04-26 20:10 ` Ben Greear 2016-04-27 6:43 ` Krishna Chaitanya [this message] 2016-04-27 6:43 ` Krishna Chaitanya 2016-04-27 9:16 ` Jouni Malinen 2016-04-27 9:16 ` Jouni Malinen 2016-04-27 9:37 ` Krishna Chaitanya 2016-04-27 9:37 ` Krishna Chaitanya 2016-04-27 9:45 ` Johannes Berg 2016-04-27 9:45 ` Johannes Berg 2016-05-06 18:08 ` Valo, Kalle 2016-05-06 18:08 ` Valo, Kalle
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='CABPxzY+UuCABUcFbV0EpdoRaSzpgGvMani_j7xvg2a=xh-Bw0g@mail.gmail.com' \ --to=chaitanya.mgit@gmail.com \ --cc=ath10k@lists.infradead.org \ --cc=greearb@candelatech.com \ --cc=johannes@sipsolutions.net \ --cc=kvalo@qca.qualcomm.com \ --cc=linux-wireless@vger.kernel.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: linkBe 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.