Thank you for providing the system information! You’re running BSP 7.4.0-devel with kernel 6.6.101 on a Colibri iMX8QXP V1.0D with the TDX Wayland with XWayland distribution.
Display Configuration for Colibri iMX8X
Your setup uses the mxsfb-drm driver for the parallel RGB interface (1). The Colibri iMX8X display configuration shows:
| Description | Parallel RGB |
|---|---|
| Device-Tree Node Reference | panel_dpi |
| DRM Driver | mxsfb-drm |
| DRM Card | card1 |
| DRM Connector Name | DPI-1 |
Known DRM Driver Issues
The coordinate transformation issues you’re experiencing with the mxsfb-drm driver appear to be related to kernel-level DRM implementation problems. Similar issues have been documented with i.MX DRM drivers where the driver implementation has limitations (2).
Potential Solutions
1. Device Tree Configuration
Ensure your device tree overlay properly configures the display chain. For newer kernels, bridges must be declared and properly connected (3). The device tree should include proper port and endpoint nodes to connect the controller to any bridge components (3).
2. Kernel Configuration Check
Since you’re on a development build (7.4.0-devel), consider checking if this is a known issue in the specific kernel version. The documentation indicates that some configurations and drivers may adversely affect performance and functionality (4).
3. Alternative Approaches
- Wayland/Weston Compositor: Since you’re using TDX Wayland with XWayland, the Wayland compositor may handle transformations differently than X.Org
- Direct DRM/KMS: Consider bypassing X.Org transformations and handling rotation at the application level using direct DRM/KMS calls
Building Custom Kernel
If needed, you can build a custom kernel with patches to address the mxsfb-drm driver issues. The build process is documented for BSP 7.x (5), though note that building from source may affect graphical functionality compared to the official BSP (5).
The coordinate transformation bug you’ve identified in the mxsfb-drm driver appears to be a kernel-level issue that may require driver-level fixes or workarounds at the compositor level.
Best regards, Toradex AI Assistant.
**
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.