[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <569d434d-cf5b-6ab0-5931-41b21ab047b7@nbd.name>
Date: Mon, 18 Oct 2021 12:16:00 +0200
From: Felix Fietkau <nbd@....name>
To: Kalle Valo <kvalo@...eaurora.org>,
Nick Hainke <vincent@...temli.org>
Cc: lorenzo.bianconi83@...il.com, ryder.lee@...iatek.com,
davem@...emloft.net, kuba@...nel.org, matthias.bgg@...il.com,
sean.wang@...iatek.com, shayne.chen@...iatek.com,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
Robert Foss <robert.foss@...aro.org>
Subject: Re: [RFC v2] mt76: mt7615: mt7622: fix ibss and meshpoint
On 2021-10-09 10:32, Kalle Valo wrote:
> Nick Hainke <vincent@...temli.org> writes:
>
>> Fixes: d8d59f66d136 ("mt76: mt7615: support 16 interfaces").
>
> The fixes tag should be in the end, before Signed-off-by tags. But I can
> fix that during commit.
>
>> commit 7f4b7920318b ("mt76: mt7615: add ibss support") introduced IBSS
>> and commit f4ec7fdf7f83 ("mt76: mt7615: enable support for mesh")
>> meshpoint support.
>>
>> Both used in the "get_omac_idx"-function:
>>
>> if (~mask & BIT(HW_BSSID_0))
>> return HW_BSSID_0;
>>
>> With commit d8d59f66d136 ("mt76: mt7615: support 16 interfaces") the
>> ibss and meshpoint mode should "prefer hw bssid slot 1-3". However,
>> with that change the ibss or meshpoint mode will not send any beacon on
>> the mt7622 wifi anymore. Devices were still able to exchange data but
>> only if a bssid already existed. Two mt7622 devices will never be able
>> to communicate.
>>
>> This commits reverts the preferation of slot 1-3 for ibss and
>> meshpoint. Only NL80211_IFTYPE_STATION will still prefer slot 1-3.
>>
>> Tested on Banana Pi R64.
>>
>> Signed-off-by: Nick Hainke <vincent@...temli.org>
>
> Felix, can I take this to wireless-drivers? Ack?
Acked-by: Felix Fietkau <nbd@....name>
Powered by blists - more mailing lists