Skip to content
Recovery Console CI

drm: port to TWRP-style atomic KMS pipeline with ADDFB2 Switch from legacy DRM_IOCTL_MODE_ADDFB to ADDFB2 with explicit fourcc pixel format driven by COLOR_BGR (XBGR8888 vs XRGB8888). This fixes black screen on panels that only accept BGR channel order. Replace hand-rolled atomic ioctl packing with a clean AtomicReq helper (atomic_begin/obj/prop/commit) and use it throughout: - atomic_modeset(): full connector+CRTC+plane commit with mode blob, source/dest rects, and connector CRTC_ID binding for... #5

Sign in to view logs

drm: port to TWRP-style atomic KMS pipeline with ADDFB2 Switch from legacy DRM_IOCTL_MODE_ADDFB to ADDFB2 with explicit fourcc pixel format driven by COLOR_BGR (XBGR8888 vs XRGB8888). This fixes black screen on panels that only accept BGR channel order. Replace hand-rolled atomic ioctl packing with a clean AtomicReq helper (atomic_begin/obj/prop/commit) and use it throughout: - atomic_modeset(): full connector+CRTC+plane commit with mode blob, source/dest rects, and connector CRTC_ID binding for...

drm: port to TWRP-style atomic KMS pipeline with ADDFB2 Switch from legacy DRM_IOCTL_MODE_ADDFB to ADDFB2 with explicit fourcc pixel format driven by COLOR_BGR (XBGR8888 vs XRGB8888). This fixes black screen on panels that only accept BGR channel order. Replace hand-rolled atomic ioctl packing with a clean AtomicReq helper (atomic_begin/obj/prop/commit) and use it throughout: - atomic_modeset(): full connector+CRTC+plane commit with mode blob, source/dest rects, and connector CRTC_ID binding for... #5

Triggered via push April 20, 2026 20:01
@ravindu644ravindu644
pushed 3a859c5
main
Status Success
Total duration 3m 4s
Artifacts 1

ci.yml

on: push
Build Recovery Console
3m 0s
Build Recovery Console
Create GitHub Release
0s
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Build Recovery Console
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
recovery-console-artifacts Expired
2.53 MB
sha256:9c9f79b4257d8eb518bc832c44eb1df6afaa531107c0e71c1b2e771b750ff590