That is way more useful. Thank you. I’m looking at this between things today. I don’t know if that is the correct screen controller for sure, but it is the best I have to go with at the moment. I’ve emailed Alex for some hopeful support.
I’ve been getting pretty frustrated trying to get it to work right for the past few days and I’ve been thinking of maybe just implementing a properly written cwu50 module for use in DKMS so that newer raspberry pi OS’s can just have a package or something to install it during runtime. I also can’t quite figure out why any of these hacks are needed at all. Looking at whatever documentation I could find on implementing a MIPI-DSI module in linux, it seems the main thing could just be improper structure of the driver itself. I don’t think the driver is effectively handling drm_bridge things, as the driver used in the 5.10 branch controls the screen totally fine. The VC4* modules had a lot of changes between then and now, and one of the biggest changes I saw looking through was based around setting up drm bridges for the kernel.
The wheel doesn’t have to be completely reinvented for any of this, but I feel as though the really janky ULPS repeat send thing and various function signature changes have caused the need for a bit of a restructuring.