Date: Wed, 31 Jul 2024 19:17:39 +0000 From: Radu-Cristian Fotescu <radu.fotescu@outlook.com> To: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: Any chance of getting mt7663 into mt76? Message-ID: <SJ0PR07MB7629EB0F927ED315A6F0196B8DB12@SJ0PR07MB7629.namprd07.prod.outlook.com> In-Reply-To: <no51q92q-p0rq-1qpn-q479-s40916qoq12q@SerrOFQ.bet> References: <SJ0PR07MB7629E6FA45BC5DCAE3699E9F8DB12@SJ0PR07MB7629.namprd07.prod.outlook.com> <no51q92q-p0rq-1qpn-q479-s40916qoq12q@SerrOFQ.bet>
index | next in thread | previous in thread | raw e-mail
> The 7663 is mt7615 Indeed, but even in Linux, 7615 needed an update/patch to have a working 7663. And it's not working great. Speed-wise is great (also BT is great), but there are warnings and timeouts in dmesg, and resuming from hibernation leads to non-working Wi-Fi and BT. So 7663 is rather poorly supported by mt7615e. But it works. > If you want you could grab a link to this > message from the mailing list archive and add a note to > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264300 I have a comprehension issue here, sorry. So I should add a note to that bug report that includes a link to this message? What for? Can't I just add something like "7663 would be a nice addition, given that it's mt7615"? It's more direct. But I don't have a FreeBSD account. I had one many years ago, but after a couple of unorthodox exchanges of ideas with des in 2007-2008, I stopped trying to use FreeBSD. Now I just attempted to assess if it could be a practical replacement for Linux. Wi-Fi and webcams are a weak point. > Any work on mt76 is still blocked on VM changes related to struct page > in LinuxKPI which I am waiting for help. I literally know nothing about LinuxKPI, and even less about those changes, or how are they blocking your work.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SJ0PR07MB7629EB0F927ED315A6F0196B8DB12>