From: Ben Greear <greearb@candelatech.com>
To: Ilya K <me@0upti.me>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [bug] Triple whammy of mt7996e bugs on 7.2+
Date: Fri, 4 Sep 2026 09:20:55 -0700 [thread overview]
Message-ID: <3acf531c-bcc7-412b-b3bb-665069260e46@candelatech.com> (raw)
In-Reply-To: <471221788538289@323ca970-5bd2-4c6b-b52d-2b863a718615>
On 9/4/26 09:11, Ilya K wrote:
>> https://github.com/greearb/linux-ct-7.2
> Hoo boy that's a lot of patches. Anything specific in there, or do you want me to just rebase my changes on that entire branch? I can try, I guess, but probably not today...
>
I don't have a good answer for you...it *is* a lot of patches, and I'm not sure if any of it
would actually help your system. We do have this kernel working for an ARM based AP that uses
mtk7996 radio, and at one time it compiled for bpi4, but I'm not sure bpi4 still
works as we do not test it.
If you can get it to compile for your system by adding any needed patches on top, that is likely best
approach, and if that actually solves the problem, we'd be happy to consider adding any bpi4 patches
to our tree.
./build_bpi4.bash may be of some interest...that is how we built it back when we did try to support bpi4.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2026-09-04 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 14:28 [bug] Triple whammy of mt7996e bugs on 7.2+ Ilya K
2026-09-04 16:07 ` Ben Greear
2026-09-04 16:11 ` Ilya K
2026-09-04 16:20 ` Ben Greear [this message]
2026-09-04 20:26 ` Ilya K
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3acf531c-bcc7-412b-b3bb-665069260e46@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@0upti.me \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox