Messages in this thread | | | Date | Mon, 11 Oct 2021 11:12:16 +0200 | Subject | Re: [RFC v2] mt76: mt7615: mt7622: fix ibss and meshpoint | From | Nick <> |
| |
My tests on todays OpenWrt Trunk with my and without my patch showed: - MT7622: AP + AdHoc (only AP is working, in every case) - BPI-MT7615: AP + AdHoc (with and without my patch still works).
I thought something would change if I apply my patch with the HW-Addresses. However everything stays the same:
With my patch: AdHoc: Shenzhen_4e:4b:dd (38:83:9a:4e:4b:dd) AP: address: 3a:83:9a:4e:4b:dd (3a:83:9a:4e:4b:dd)
Without my patch: AdHoc: Shenzhen_4e:4b:dd (38:83:9a:4e:4b:dd) AP: 3a:83:9a:4e:4b:dd (3a:83:9a:4e:4b:dd)
Bests Nick
On 10/9/21 15:22, Daniel Golle wrote: > On Sat, Oct 09, 2021 at 12:37:53PM +0200, Nick wrote: >> On 10/9/21 10:32, Kalle Valo wrote: >> >>> Nick Hainke <vincent@systemli.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. >> Thanks for feedback. Already changed that locally but I did not want to spam >> you with another RFC v3. :) >> I was able to organize me a BPI-MT7615 PCIE Express Card. With and without >> this patch beacons were sent on the mt7615 pcie, so the patch did not make >> any difference. However, the mt7622 wifi will only work with my patch. > Does Mesh+AP or Ad-Hoc+AP also work on MT7622 and does it still work on > MT7615E card with your patch applied?
| |