On Thursday, 13 June 2024 23:00:51 CEST Leith Bade wrote: > Excellent, hopefully we can get the DTS stuff from OpenWrt upstreamed into > Linux for the OpenWrt and BPI-R3.
I have (thus far) found one possible oddity, but otherwise it looks ok AFAICT for BPI-R3. When that's done, the OpenWrt One should be rather simple. But only *IF* they upstream it in time. > I am not sure what the process is for that. The first step would be to get involved with the community. I'm quite sure there's one or more threads about the BPI-R3 on the OpenWrt forums. > As for the MT7988 I can save up and get a BPI-R4 for testing in the future, > though I have a feeling that the Debian testing kernel might be too old, > the drivers were only added to Linux 5 months ago. So maybe I will wait > until there is a Debian version with a newer kernel. I did look (briefly) into MT7988 and the problem isn't on the Debian side, but on the upstream side. Looking at the mt7988a.dtsi and it seems there's *quite* a lot missing. And the BPI-R4 dts file includes that incomplete dtsi file and then specifies the model name and chassis-type. That's it. If you compare that with BPI-R3 then you'll see a huge difference. So it looks like there's quite some work to do before the BPI-R4 is supported upstream, which is a prerequisite for support in Debian. I haven't looked (at Mailing Lists), but I would be very surprised if we could get (proper) support in the Trixie kernel. If you're interested in this kind of thing, you have enough time to learn and contribute to get proper support for it in the Forky kernel. HTH, Diederik
signature.asc
Description: This is a digitally signed message part.
