Skip to content

mesa-aurora: pin merged M3 Pro Vulkan features for the new kernel cohort - #1737

Closed
chriskearney wants to merge 1 commit into
omacom:masterfrom
chriskearney:mesa-aurora-merged-eryk-trifecta-f412
Closed

chriskearney wants to merge 1 commit into
omacom:masterfrom
chriskearney:mesa-aurora-merged-eryk-trifecta-f412

Conversation

@chriskearney

Copy link
Copy Markdown
Contributor

Pins mesa-aurora and vulkan-aurora to 7f0206e79f9f6370b4a898e6073b20d8804f31ea, Marcelo's merge of omacom/mesa#17. Its tree ef2941be… exactly equals approved/tested PR head 7c9db520.

This completes the three source pins for coordinated delivery:

Packages Source merge Package PR
linux-aurora / headers, 7.2.11.aurora9-1 30a65186 (#246/#249/#253/#240) #1735
mesa-aurora / vulkan-aurora, 1:26.3.0_devel.20261028.231099.7f0206e79f9-1 7f0206e7 (Mesa #17) This PR
m1n1-aurora, 1.6.1.aurora22-1 bc79acc4 (m1n1 #19/#17) #1707

Only pkgver, _commit and pin/qualification comments change. Build options, dependencies, LLVM/SPIRV runtime-link checks, Meson tests, split packages and channel metadata remain unchanged. The separate llvmpipe change in #1711 is not included.

The new version sorts above the current one (vercmp returns 1). Its UTC date is the merge's 2026-10-28 date. Reachable count 231099 is the previous pin's published full-history count 231095 plus the four new reachable commits: three PR commits and the merge. The compare graph confirms the old pin is the merge base, ahead 4 / behind 0. Shell syntax and git diff --check pass.

The source's aarch64/x86_64 CI passed. The targeted functional approval records 457 attributed passes, 521 reasoned skips, zero fail/missing on J516S with original kernel #233/#238 8824dd6a. The G15S feature profile exposes conditional rendering, unified image layouts and 16 descriptor sets; it does not expand the Air/Max profiles. The original retry-passing geometry issue remains recorded. The combined-stack benchmark improvement is not a Mesa-only or Air/Max speedup claim.

The final three-package combination has not been built and hardware-booted together. The source-equivalent Mesa tree and prior component tests do not qualify that exact package cohort, fresh installer, full Vulkan conformance or RC/stable promotion. Marcelo requested exact final-kernel J516C and M3 Pro boot coverage before or immediately after edge delivery; retain that follow-up.

@maralcbr please coordinate this native package build/delivery with #1735 and #1707, following the landing-order recommendation. No build-approval label, package merge, publication, installer rebuild or target installation is performed by this source-pin PR.

Pin omacom/mesa merge 7f0206e7, whose tree equals approved and functionally tested PR17 head 7c9db520. Advance the UTC-date/count/hash version monotonically; preserve package options, split, dependencies and checks. Coordinate native builds and delivery with linux-aurora#1735 and m1n1-aurora#1707. The final three-package cohort remains unbooted; component evidence and rollout qualification stay separate.

Generated-by: OpenAI Codex
Signed-off-by: Chris Kearney <303316+chriskearney@users.noreply.github.com>
@greptile-apps

greptile-apps Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] This source-pin update appears safe to merge without treating it as approval to publish or promote the packages.

Summary

Updates mesa-aurora and vulkan-aurora to source commit 7f0206e79f9f6370b4a898e6073b20d8804f31ea.

  • Aurora package builds now use the Mesa merge with the M3 Pro Vulkan profile.

Reviews (1) · Last reviewed commit: "mesa-aurora: pin merged M3 Pro Vulkan pr..." · Reviewed by Greptile

@maralcbr

Copy link
Copy Markdown
Member

Superseded by #1736, which carries this same pin (linux-aurora aurora9 30a65186 and mesa-aurora 7f0206e7, line-for-line identical) in one PR, so both build and publish together. Its build is already running. @chriskearney please close this one. #1707 follows once #1736 is on edge.

@maralcbr

Copy link
Copy Markdown
Member

Closing as superseded by #1736, which shipped the identical pin to edge.

@maralcbr maralcbr closed this Oct 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants