Repository navigation
Conversation
|
Thank you, @cx3301J. An opt-in overlay with the nodes disabled in the kernel is just what I asked for, and the file compiles and applies cleanly to #202's 7a device tree. I checked it with that PR's build. Before it can go in:
Two small things: the file is executable (mode 755), while every other overlay is 644. And CONTRIBUTING §7 asks for |
8046a5c to
b57ac89
Compare
The base DTS ships DSIM0, DECON0 and the display clocks disabled. This overlay turns them on for a phone with the S6E3FC5 panel. Signed-off-by: cx3301J <cx3301J@users.noreply.github.com> Assisted-by: DeepSeek
b57ac89 to
f94f424
Compare
|
Rebased onto main c462357 and fixed the stray closing brace that was left when the GPU fragment was removed. Head 94f424. Assisted-by: DeepSeek |
|
Thank you, @cx3301J. The GPU fragment is gone and the commit message matches the file now, which settles that point: #202's board file turns the GPU on itself. The red check isn't yours. It is a timing case in the shell package's power-key test ( I built the 7a's device tree from today's published kernel and from #202's head and applied the overlay to both. On #202 it does what it should: DSIM0 with the S6E3FC5 panel, DECON0 with its pool and the boot framebuffer, and the two display clock controllers. On today's published kernel it also applies, and there it turns on DECON0 with no scanout pool and DSIM0 with no panel under it. So the points from last time still stand:
Order of merging: #438 first (its unit does nothing until the DECON node is enabled), then #202, then this one. |
The 7a's bootloader leaves 0x1cf8 and 0x2a82306d in DSIM0 at 60 Hz; derekross#181's Pixel 7 row is the same pair. Assisted-by: DeepSeek Signed-off-by: cx3301J <cx3301J@users.noreply.github.com>
The kernel's lynx DTS now leaves DSIM0, DECON0, the display clocks and the GPU disabled. This overlay turns them on for a phone with the S6E3FC5 panel, so a board without it keeps the bootloader framebuffer.
Part of linux-omarchy-mobile#202.