<div dir="ltr">Hello,<div><br></div><div>Vehicular communications is an interesting push-point to get ad-hoc support in Wi-Fi, as car vendors may see sufficient value in it to push things along.</div><div><br></div><div>How much 802.11p stuff is out there?</div>
<div><br></div><div>Paul.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 30, 2014 at 4:16 AM, Josh King <span dir="ltr"><<a href="mailto:jking@opentechinstitute.org" target="_blank">jking@opentechinstitute.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sort of. 802.11p doesn't even attempt to establish a BSS, it just<br>
broadcasts and receives on the wildcard BSSID. So it doesn't use ad-hoc<br>
mode as we would normally use it, but it seems like you could implement<br>
it by setting up an ad-hoc network on the wildcard BSSID without many if<br>
any driver changes.<br>
<br>
On 07/29/2014 12:25 PM, Kirk Reiser wrote:<br>
> However, isn't it adhoc mode that all the auto manufacturers are using<br>
> for intervehicle communication? That would certainly increase the<br>
> demand for it. I aggree not supporting it would be shooting oneself in<br>
> the foot commercially.<br>
><br>
> On Mon, 28 Jul 2014, Ben West wrote:<br>
><br>
>> Typos ahoy! "Result in *insufficient* performance..."<br>
>><br>
>><br>
>> On Mon, Jul 28, 2014 at 4:02 PM, Ben West <<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a>> wrote:<br>
>><br>
>>> The unfortunate detail is that adhoc mode is not especially favored by<br>
>>> many commercial vendors (Qualcomm included), and a prevailing opinion<br>
>>> among<br>
>>> them is that the IEEE 802.11 spec for adhoc in particular is<br>
>>> inadequate for<br>
>>> modern implementation. Indeed, in lieu of the electromagnetic<br>
>>> calisthenics<br>
>>> involved in doing MIMO under 802.11ac (use which channels? why, ALL of<br>
>>> them!), they readily can jump to the conclusion including adhoc support<br>
>>> would result in sufficient performance, so they won't do it.<br>
>>><br>
>>><br>
>>> On Mon, Jul 28, 2014 at 3:09 PM, Griffin Boyce <<a href="mailto:griffin@cryptolab.net">griffin@cryptolab.net</a>><br>
>>> wrote:<br>
>>><br>
>>>> Yes, it seems quite strange that they would shoot themselves in the<br>
>>>> foot<br>
>>>> like that. I'm withholding judgment in the absence of more information.<br>
>>>><br>
>>>> ~ Griffin<br>
>>>><br>
>>>><br>
>>>> On July 26, 2014 5:54:45 PM EDT, Ben West <<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a>> wrote:<br>
>>>>><br>
>>>>> It's odd then that IBSS-related patches have submitted to ath10k this<br>
>>>>> year:<br>
>>>>> <a href="http://lists.infradead.org/pipermail/ath10k/2014-February/001159.html" target="_blank">http://lists.infradead.org/pipermail/ath10k/2014-February/001159.html</a><br>
>>>>><br>
>>>>> Likewise, the ath10k driver page doesn't mention the absence of<br>
>>>>> IBSS/adhoc support (which one would expect to be a rather large<br>
>>>>> omission<br>
>>>>> worth pointing out):<br>
>>>>> <a href="http://wireless.kernel.org/en/users/Drivers/ath10k" target="_blank">http://wireless.kernel.org/en/users/Drivers/ath10k</a><br>
>>>>><br>
>>>>> Looks like the difference arose b/w versions 999.999.0.x and 10.1.x of<br>
>>>>> the (closed-source?) firmware:<br>
>>>>> <a href="http://wireless.kernel.org/en/users/Drivers/ath10k/firmware" target="_blank">http://wireless.kernel.org/en/users/Drivers/ath10k/firmware</a><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> On Sat, Jul 26, 2014 at 3:54 PM, Josh King<br>
>>>>> <<a href="mailto:jking@opentechinstitute.org">jking@opentechinstitute.org</a>><br>
>>>>> wrote:<br>
>>>>><br>
>>>>>> No, not yet. Mostly just being facetious. However, I am hoping<br>
>>>>>> that this<br>
>>>>>> isn't a trend for the next generation of wifi chipsets going forward.<br>
>>>>>><br>
>>>>>> On 07/26/2014 11:30 AM, Griffin Boyce wrote:<br>
>>>>>>> *snicker*<br>
>>>>>>><br>
>>>>>>> Now, now, let's not let our emotions get the better of us. I'm sure<br>
>>>>>> that<br>
>>>>>>> the other Aetheros chipsets are plenty good ;)<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> On July 25, 2014 10:21:24 PM EDT, Josh King<br>
>>>>>>> <<a href="mailto:jking@opentechinstitute.org">jking@opentechinstitute.org</a>> wrote:<br>
>>>>>>><br>
>>>>>>> *Flips table*<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> On July 25, 2014 7:53:12 PM EDT, Will Hawkins<br>
>>>>>>> <<a href="mailto:hawkinsw@opentechinstitute.org">hawkinsw@opentechinstitute.org</a>> wrote:<br>
>>>>>>><br>
>>>>>>> It looks like the ath10k does not support IBSS.<br>
>>>>>>><br>
>>>>>>> Will<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> -------- Original Message --------<br>
>>>>>>> Subject: [PATCH] ath10k: don't advertise IBSS iftype for<br>
>>>>>>> 10.x<br>
>>>>>>> Date: Wed, 23 Jul 2014 11:58:09 +0200<br>
>>>>>>> From: Michal Kazior <<a href="mailto:michal.kazior@tieto.com">michal.kazior@tieto.com</a>><br>
>>>>>>> To: <a href="mailto:ath10k@lists.infradead.org">ath10k@lists.infradead.org</a><br>
>>>>>>> CC: <a href="mailto:linux-wireless@vger.kernel.org">linux-wireless@vger.kernel.org</a>, Michal Kazior <<br>
>>>>>> <a href="mailto:michal.kazior@tieto.com">michal.kazior@tieto.com</a>><br>
>>>>>>><br>
>>>>>>> The 10.x firmware does not support IBSS mode at<br>
>>>>>>> all. It can't beacon and it crashes when trying to<br>
>>>>>>> scan.<br>
>>>>>>><br>
>>>>>>> Signed-off-by: Michal Kazior <<a href="mailto:michal.kazior@tieto.com">michal.kazior@tieto.com</a>><br>
>>>>>>> ---<br>
>>>>>>> drivers/net/wireless/ath/ath10k/mac.c | 3 ++-<br>
>>>>>>> 1 file changed, 2 insertions(+), 1 deletion(-)<br>
>>>>>>><br>
>>>>>>> diff --git a/drivers/net/wireless/ath/ath10k/mac.c<br>
>>>>>>> b/drivers/net/wireless/ath/ath10k/mac.c<br>
>>>>>>> index 3f9afaa..5122d1b 100644<br>
>>>>>>> --- a/drivers/net/wireless/ath/ath10k/mac.c<br>
>>>>>>> +++ b/drivers/net/wireless/ath/ath10k/mac.c<br>
>>>>>>> @@ -4700,7<br>
>>>>>>> +4700,6 @@ int ath10k_mac_register(struct ath10k *ar)<br>
>>>>>>><br>
>>>>>>> ar->hw->wiphy->interface_modes =<br>
>>>>>>> BIT(NL80211_IFTYPE_STATION) |<br>
>>>>>>> - BIT(NL80211_IFTYPE_ADHOC) |<br>
>>>>>>> BIT(NL80211_IFTYPE_AP);<br>
>>>>>>><br>
>>>>>>> if (test_bit(ATH10K_FW_FEATURE_WMI_10X,<br>
>>>>>>> ar->fw_features)) {<br>
>>>>>>> @@ -4770,6 +4769,8 @@ int ath10k_mac_register(struct ath10k<br>
>>>>>> *ar)<br>
>>>>>>> ar->hw->wiphy->iface_combinations = ath10k_if_comb;<br>
>>>>>>> ar->hw->wiphy->n_iface_combinations =<br>
>>>>>>> ARRAY_SIZE(ath10k_if_comb);<br>
>>>>>>> +<br>
>>>>>>> + ar->hw->wiphy->interface_modes |=<br>
>>>>>> BIT(NL80211_IFTYPE_ADHOC);<br>
>>>>>>> }<br>
>>>>>>><br>
>>>>>>> ar->hw->netdev_features = NETIF_F_HW_CSUM;<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> --<br>
>>>>>>> Sent from my tracking device. Please excuse brevity and cat photos.<br>
>>>>>><br>
>>>>>> --<br>
>>>>>> Josh King<br>
>>>>>> Lead Technologist<br>
>>>>>> The Open Technology Institute<br>
>>>>>> <a href="http://opentechinstitute.org" target="_blank">http://opentechinstitute.org</a><br>
>>>>>> PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999<br>
>>>>>><br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> Commotion-dev mailing list<br>
>>>>>> <a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
>>>>>> <a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
>>>>>><br>
>>>>>><br>
>>>>><br>
>>>>><br>
>>>> --<br>
>>>> Sent from my tracking device. Please excuse brevity and cat photos.<br>
>>>><br>
>>><br>
>>><br>
<span class="HOEnZb"><font color="#888888">>>><br>
>>> --<br>
>>> Ben West<br>
>>> <a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br>
>>> <a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a><br>
>>> 314-246-9434<br>
>>><br>
>><br>
>><br>
>><br>
>><br>
><br>
<br>
--<br>
Josh King<br>
Lead Technologist<br>
The Open Technology Institute<br>
<a href="http://opentechinstitute.org" target="_blank">http://opentechinstitute.org</a><br>
PGP Fingerprint: 8269 ED6F EA3B 7D78 F074 1E99 2FDA 4DA1 69AE 4999<br>
<br>
</font></span><br>_______________________________________________<br>
Commotion-dev mailing list<br>
<a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
<br></blockquote></div><br></div>