[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YWGXiExg1uBIFr2c@makrotopia.org>
Date: Sat, 9 Oct 2021 14:22:16 +0100
From: Daniel Golle <daniel@...rotopia.org>
To: Nick <vincent@...temli.org>
Cc: Kalle Valo <kvalo@...eaurora.org>, nbd@....name,
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 Sat, Oct 09, 2021 at 12:37:53PM +0200, Nick wrote:
> On 10/9/21 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.
> 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?
Powered by blists - more mailing lists