marfrit/marfrit-packages
0
0
Fork 1
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: marfrit/marfrit-packages:e7cc22e42db42a7d7590e21e9d1d0bad8ba25cba
Branches Tags
marfrit/marfrit-packages:main
..
compare: marfrit/marfrit-packages:8a3186b53c29cf6a875eafeed51b80fa0ab6f28f
Branches Tags
marfrit/marfrit-packages:main

2 Commits
e7cc22e42d .. 8a3186b53c

Author SHA1 Message Date
marfrit 8a3186b53c Merge pull request 'mesa-panvk-bifrost-video: re-trigger Actions for PR #79' (#80) from claude-noether/marfrit-packages:noether/mesa-panvk-bifrost-video-retrigger into main 
Reviewed-on: #80
 2026-05-22 06:32:42 +00:00
marfrit b81e2251c2 mesa-panvk-bifrost-video: re-trigger Actions for PR #79 
The merge commit for PR #79 (e7cc22e42) did not auto-fire the
Gitea Actions workflow despite touching paths matched by the
build.yml filter (arch/** + .gitea/workflows/**). No run row
exists between #160 (PR #78 merge) and now. This README touch
is a no-op content change to force a fresh workflow_dispatch
through the standard push trigger.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
 2026-05-22 07:51:01 +02:00
1 changed files with 1 additions and 1 deletions
Expand all files Collapse all files
arch/mesa-panvk-bifrost-video/README.md
+1 -1
View File
@@ -6,7 +6,7 @@ This is a **sibling** of [mesa-panvk-bifrost](../mesa-panvk-bifrost/) (the r4 pa
## Status
Phase 4 byte-exact validated 2026-05-21: 48/48 unique BBB display frames decoded by this package are byte-identical to `ffmpeg+libva-v4l2-request-fourier` running on the same hantro hardware. Phase 5 second-model review completed; all load-bearing findings addressed.
Phase 4 byte-exact validated 2026-05-21: 48/48 unique BBB display frames decoded by this package are byte-identical to `ffmpeg+libva-v4l2-request-fourier` running on the same hantro hardware. Phase 5 second-model review completed; all load-bearing findings addressed. First publish via marfrit-packages CI 2026-05-22 (PR #79 merge did not auto-fire Actions; this re-trigger restores the standard build/sign/publish path).
## How to use