Skip to content

drm/asahi: t6050: identify the K114/K116 27.2 (26B8125) G17S firmware (on #1173) - #1650

Draft
sithglan wants to merge 13 commits into
aurora-silicon:integration/aurorafrom
sithglan:thomas/k116s-gpu-26b8125
Draft

sithglan wants to merge 13 commits into
aurora-silicon:integration/aurorafrom
sithglan:thomas/k116s-gpu-26b8125

Conversation

@sithglan

@sithglan sithglan commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Stacked on #1173 (Rolando's M5 27.2/27.3 InitData, draft). The branch preserves #1173's head d8ca53c and Jens's firmware-identity commit, followed by a merge of integration/aurora a7dd26e on 2026-11-17. Please merge after #1173; the firmware-identity change remains Jens's original commit. The same arrangement as #1602.

drm/asahi: t6050: identify the 27.2 (26B8125) G17S firmware of the K114/K116. The 16-inch M5 Pro OLED (K116s, Mac17,12) restores from UniversalMac_27.2_26B8125, not from the 26B123 image #1173 pins. Its a010 G17S images are the ones iBoot loads: their LC_UUIDs are the K116s ADT's iop-gfx-nub and iop-gfx1-nub uuid. TEXT, DATA, the GKTS/ECAP records and the tunables/patchbay sections sit at 26B123's offsets, but the fwid digest differs (af68d034...f38f6cb against 26B123's 2b4613c6...913f0fd9). Without this entry the driver refuses the K116s firmware before any GPU write. It uses V26B123_M5, because the 26B8125 kernelcache's AGX kext builds the 26B123 root version word and allocation sizes.

Tested by Jens on the K116s: the kernel driver initialises on 26B8125, Vulkan works (vkcube) and Plasma composites on it, with ASAHI_M5_BRINGUP=1. The commit message still says "no 27.2 firmware has run this graph on hardware". It predates that test, and I left Jens's text as it is.

Not included: Jens's "K116s board tables, selected by apple,agx-g17s-k116". It says itself that it is a local bring-up patch: the K116s voltages are most likely per unit, and the right fix is a loader hand-off of the ADT tables. Without it the K116s uses the J714 tables. The K116s DT PR #1648 leaves the GPU compatible at apple,agx-g17s to match.

The 2026-11-17 target merge resolves the overlapping M5 InitData and variant changes. Firmware-version layouts now select the current Graph representation; the target’s J813 common-26 encoding, board offsets, controller defaults and cached submission-history reads are retained. The 27.2/27.3 status-history fields use their firmware-specific relocation. No original commit was rewritten.

This touches the same Build list in hw/t6050.rs as #1602 (Joshua's 27.3 26C5035r entry, also on #1173). The two entries are independent, but whichever lands second needs a trivial rebase.

Validation of merge c6abd0b against integration/aurora a7dd26e: ARM64 LLVM 22.1.8/Rust 1.98.1 drivers/gpu/drm/asahi/ build passes with both CONFIG_DRM_ASAHI_M5=y and CONFIG_DRM_ASAHI_G18=y; 90/90 G17 host runs and the asahi-m4 host suite pass. A Rust parity harness checks 18 byte-identical artifacts: current-target J714/J716C/J775D/J813 default hardware/private/policy encodings, and original #1173 26A428/26B123/26C5035 private/policy encodings. It also checks Graph offsets, submission-history relocation, kick pointers and enabled-core fields. Existing unused-code warnings remain. The refreshed merge has not been booted on K116s or J813; Jens’s hardware results above apply to his earlier tree, not this refresh.

Authorship. Jens Axboe wrote the new commit and runs it on his K116s (16-inch MacBook Pro, M5 Pro, OLED; Mac17,12; stub macOS 27.2 26B8125). It comes from his K116s bundle of 2026-11-11 (integration/aurora 254c9bd plus 34 commits, kernel 7.3.0 running on the machine). I rebased it onto #1173's head d8ca53c and removed the LLM co-author and session trailers. Jens has given his OK: the commit carries his Signed-off-by. The #1173 commits are Rolando's, unchanged.

rolotrealanis98 and others added 11 commits November 10, 2026 05:55
…cannot build

From macOS 27.2 on, the M5 GPU firmware expects a different InitData
graph than the 26A428 (27.0) one the M5 path builds:

- the root version word gains bit 46 (0x0c8e_0339_8728_04c0 ->
  0x0c8e_4339_8728_04c0), in 27.2 and 27.3 alike;
- the power policy grows from 0x126b0 to 0x12728 bytes and the status
  config from 0x780 to 0x790, in 27.2 and 27.3 alike;
- 27.3 beta 1 alone inserts a HW data word at 0x2720.

These layouts are not yet confirmed from captured InitData of a
running macOS; the later commits of this series say which parts a
running firmware has accepted.

Name the layouts a build needs (Variant::m5_layouts) and give the 27.2
firmware its own variant, V26B123_M5: the 26A428 M5 protocol with the
26B123 layouts. Until the M5 graph builds them, Gpu::new() refuses such
a build right after identifying it, before anything is written to the
GPU, instead of handing it a graph it would reject ("Host and FW
Interface is mismatched") or misread.

Every M5 build in the tree today is 26A428 and names
M5Layouts::V26A428, so nothing changes for the M5 Max and M5 Ultra.

Signed-off-by: Rolando Trevino <rolotrealanis@gmail.com>
Assisted-by: LLM Claude
…uilds

The M5 Pro admits only the 27.0 (26A428) G17S build. Pin the 27.2
(26B123) and 27.3 beta 1 (26C5035r) G17S builds of both roles as well,
measured the way fwid defines a build (the SHA-256 of the primary's
then the secondary's TEXT with the entropy records, the two header
load fields and the two boot-argument sections of each role zeroed):

  27.3 beta 1 (26C5035r)  b5537c8f06bd...66763600
  27.2 (26B123)           2b4613c62a8a...913f0fd9

The images are the G17S (FW Build variant a010) primary and secondary
GFX firmware of the public Mac17,8 IPSW for 27.2 and of the 27.3 beta
1 restore bundle (im4p SHA-256 ae7f35b1... and da8ff3fb...). The
offsets come from each image's Mach-O load commands: text at 0x50000 +
0x54000, DATA 0x184000 as on the M5 Max, the _rtk_tunables and
_rtk_patchbay sections per role. 27.2 needs an entry
of its own although its interface matches 27.3's: its primary entropy
record sits at 0x49ea4, 27.3's at 0x49eac. Each image header still
carries its load fields at 0x224/0x23c (zero in the file, the
patchbay's offset and size at 0x22c/0x230, as in 26A428).

The 27.0 entry is the one the base already pins: this digest procedure
gives the same digest for it, and reproduces the two pinned 26A428
digests of the M5 Max (G17C) and M5 Ultra (G17D).

27.0 runs the 26A428 graph. 27.2 and, for now, 27.3 name V26B123_M5,
whose layouts the M5 graph does not build yet, so they are identified
and then refused before any GPU write; 27.3 gets its own variant once
its HW data is built. The fwid KUnit tests cover the new builds.

Signed-off-by: Rolando Trevino <rolotrealanis@gmail.com>
Assisted-by: LLM Claude
The M5 GPU firmware of macOS 27.2 (26B123) is expected to find a
different root version word than 27.0 (26A428):
0x0c8e_4339_8728_04c0 where 27.0 has 0x0c8e_0339_8728_04c0, only bit
46 differs.

Its allocation size table differs from 26A428's
(ABI_ALLOCATION_SIZES_26A428_M5) in two entries only:

  index 4,  power policy:  0x126b0 -> 0x12728
  index 13, status config: 0x780   -> 0x790

The packed layouts derived from it move accordingly: in the shared
cluster everything after the policy moves by 0x80 (views 3 and 4, the
BRN table and repeated region, the twelve DM rings, both main configs
and control rings); in the private cluster everything after the status
config moves by 0x40 (both role sets with status A, the secondary
control state, secondary extra 1 and the policy state). Both clusters
keep their page-rounded sizes (0x34000 and 0x178000), so the fixed
windows of the M5 graph still hold them. The HW data of 26B123 is
26A428's.

The version word, the sizes and the HW data layout of 26B123 are not
yet confirmed from captured InitData.

Describe one firmware build's InitData layout as an M5Layout (its size
table, the packed clusters derived from it, and how its HW data moves
relative to the 26A428 encoding), add M5_LAYOUT_26A428 and
M5_LAYOUT_26B123, and a RootProfile J714G17S26B123 that writes the new
version word and takes its offsets from the 26B123 layout. build_m5()
now takes the firmware build's Variant and builds the profile its
M5Layouts names.

Gpu::new() keeps refusing every build but 26A428 until the 26B123
power policy and status config are laid out as well (later in this
series), so no firmware is handed a partly converted graph.

The 26A428 encodings are unchanged: the HW data of every board, the
private cluster, the bundle policy, both roots and both main configs
encode to the same bytes as before.

Signed-off-by: Rolando Trevino <rolotrealanis@gmail.com>
Assisted-by: LLM Claude
The M5 firmware of macOS 27.3 beta 1 (26C5035r) takes the 26B123
version word and allocation sizes, but its HW data is not 26B123's:
one u32 is inserted at 0x2720 and every later field moves by 4 (the
kick-shared pointer from 0x27dc to 0x27e0, the last moved word from
0x2846 to 0x284a; everything below 0x2720 is as before). The version
word does not tell the two builds apart; only the firmware identity
does.

The new word is the time the GPU may take to reach a forced idle after
a sleep request, in ms; 0 disables the wait. The value written,
5000, is 5 s times 1000. The layout, the meaning of the word and the
value are not yet confirmed from captured InitData.

Describe the move with the layout bands the HW data already uses
(M5_26C5035_HW_DATA_BANDS: 0..0x2720 stays, 0x2720..0x284c moves by
4; the four bytes it drops past 0x284c are zero in the 26A428
encoding), apply them after the 26A428 encoding and write the word,
and find the kick-shared pointer and the enabled-core words through
them. Add RootProfile J714G17S26C5035, M5Layouts::V26C5035 and its
Variant V26C5035_M5, and have the 27.3 (26C5035r) G17S build of the
M5 Pro name it instead of V26B123_M5. The fwid KUnit test that checks
each M5 Pro build's layouts follows.

The encoded 26C5035r HW data of every board equals the 26A428
encoding below 0x2720, has 5000 at 0x2720 and carries the 26A428
bytes 0x2720..0x284c at 0x2724.

Signed-off-by: Rolando Trevino <rolotrealanis@gmail.com>
Assisted-by: LLM Claude
The 26B123 M5 firmware takes a 0x12728-byte power policy instead of
0x126b0 (allocation size table entry 4); 27.3 beta 1 (26C5035r) has
the same layout. Five inserts, as bands in 26A428 offsets, move the
words above them:

  [0x0000, 0x4910)   +0
  [0x4910, 0x491c)   +0x10  two u64 words; the three controller input
                            words at 0x4910 (3500/1000/3000 in the J714
                            defaults) move to 0x4920
  [0x491c, 0x49b8)   +0x14  a controller input word at 0x492c
  [0x49b8, 0x4a98)   +0x18  4 bytes between 0x494c and 0x49b8 that the
                            M5 encoders do not write
  [0x4a98, 0x12668)  +0x30  0x18 bytes between 0x4a00 and 0x4a98 that
                            they do not write either
  [0x12668, 0x126b0) +0x78  the table at +0x122f0 grows from 37 to 40
                            24-byte entries

The state and AON PTD pointers move to 0x8284 and 0x11a4c. The 26B123
policy may use words of its own at 0x94e4..0x954c, in space the M5
encoders do not write in 26A428; they stay zero here.

The policy controller input words the 26B123 policy carries beyond the
26A428 ones are 0x492c = 5000 and 0x4a14 = 1600 (26A428 0x49fc, 500 in
the J714 defaults) for the core types 0x18/0x19, and for the G17D core
type 0x1a 0x4920 = 2500, 0x4928 = 800, 0x492c = 1100, 0x49e4 = 0 and
0x4a14 = 1600. These values and the bands above are not yet confirmed
from captured InitData; they are what a capture session has to check.

Add M5PolicyMap with the 26A428 identity map and the 26B123 map, chosen
from the build's M5Layouts (every layout but 26A428 takes the 26B123
map), and relayout_m5_policy(), which moves the bands of the policy the
26A428 encoders wrote in place, highest first, zeroes the inserts and,
where the board's controller defaults were applied, writes the 26B123
controller words for its core type. For 26A428 it changes nothing.

Not run on hardware: the controller words (they are written only where
the board's controller defaults apply, and no run of this layout has
had them) and the G17D (J775D) words on 26B123; no 27.2+ M5 Max or
M5 Ultra firmware is identified yet.

Signed-off-by: Rolando Trevino <rolotrealanis@gmail.com>
Assisted-by: LLM Claude
The M5 graph's policy encoders (encode_m5_bundle_policy() and the
boards' controller defaults) write the 26A428 layout. Keep the build's
policy map in InitData, set through set_m5_policy_layouts() from the
identified firmware's M5Layouts, and lay the policy out for it in
build_m5() once the controller defaults have run: the 26B123 layout
moves every word above 0x4910 and adds the 26B123 controller words
where the board's defaults applied. The maximum-power word read for
region C (0xa18) does not move.

The relayout stays within the build's own policy allocation: a policy
larger than the space before block_68 of the shared layout is refused.
The diagnostic policy read is bounded by the build's policy size.

The map defaults to 26A428, so the 26A428 graph is unchanged.

Signed-off-by: Rolando Trevino <rolotrealanis@gmail.com>
Assisted-by: LLM Claude
The 26B123 M5 firmware takes a 0x790-byte status config instead of
0x780 (allocation size table entry 13); 27.3 beta 1 (26C5035r) has the
same layout. Everything up to +0x5b4 keeps its offset. From +0x5b4 the
object holds two controller blocks, at +0x5b4 and +0x610, of 0x5c
bytes each. 26B123 inserts two words into each block, an override slot
at block +0x28 and its value at block +0x58, so a block grows to 0x64
bytes, and everything after the second block moves by 0x10: the link
word and pointer (0x774/0x778 -> 0x784/0x788) and the submission
history (0x73c/0x74c/0x750 -> 0x74c/0x75c/0x760).

As bands in 26A428 offsets: [0, 0x5dc) +0, [0x5dc, 0x608) +4,
[0x608, 0x638) +8, [0x638, 0x664) +0xc, [0x664, 0x780) +0x10. The new
words are 0x5dc and 0x640 (override slots, zero-filled) and 0x60c
(5000) and 0x670 (0), the values. The layout and these values are not
yet confirmed from captured InitData.

Add M5StatusConfigMap with the 26A428 identity map and the 26B123 map,
encode the primary status-B span through it, and read the submission
history through the map the graph was built with. The 26A428 status
config is unchanged: the map path writes the same 0x780 bytes as
write_relocated_words() with COMMON26_STATUS_CONFIG_BANDS. The 26A428
words the driver writes from 0x5a4 are not changed here; the 26B123
map moves them like every other word.

Signed-off-by: Rolando Trevino <rolotrealanis@gmail.com>
Assisted-by: LLM Claude
Give RootProfile the status-config map of its M5 graph and have
build_m5() pick the profile before it encodes the private cluster, so
the status-B span, the link word and pointer and the submission-history
reader all follow the profile's layout. Every existing profile keeps
the 26A428 map, so the graph is unchanged.

Signed-off-by: Rolando Trevino <rolotrealanis@gmail.com>
Assisted-by: LLM Claude
…3 profiles

The 26B123 (macOS 27.2) firmware takes the 0x790-byte status config:
two words more in each controller block and the tail, link word and
submission history 0x10 higher. Return M5_26B123_STATUS_CONFIG for the
26B123 root profile, and for the 26C5035 (macOS 27.3 beta 1) profile,
whose status config is the same as 26B123's.

Signed-off-by: Rolando Trevino <rolotrealanis@gmail.com>
Assisted-by: LLM Claude
…e firmware build

build_m5() now selects the power-policy map from the same M5 layouts
the root profile comes from, so a 26B123 or 26C5035 firmware gets its
policy laid out to 0x12728 bytes and its 0x790-byte status config in
the same graph. The policy and status-config sizes of 26B123 are
entries 4 and 13 of its allocation size table, and a compile-time
check holds every M5 build's policy and status-config maps to its own
size table, with the policy at the offset the controller defaults
write it.

The controller defaults keep writing the 26A428 policy, which the
relayout then moves; name that slice once. The private cluster encoder
takes the root profile and derives both the cluster layout and the
status-config map from it, which leaves the 26A428-only status-B
wrapper without callers.

With every 27.2+ layout in place, Gpu::new() now refuses only a build
that names no M5 layouts, so the M5 Pro's 27.2 (26B123) and 27.3 beta 1
(26C5035r) builds run their graphs. 26A428 builds, the only ones the
M5 Max and M5 Ultra identify, take the identity maps and build the
same bytes as before this series.

The 27.2+ layouts and values of this series are not yet confirmed from
captured InitData; the comments say which. What has been observed is
the following. An earlier revision of this series, with J716s board
tables and a native-address mailbox compatible that are not part of
this one, ran on a J716s (16-inch M5 Pro) with the 27.3 beta 1 boot
firmware, a device tree that describes the GPU and a loader that hands
it over (none of them part of this series):

  aurora 2300000000.gpu: GPU firmware: 27.3 (26C5035r), G17S
  aurora 2300000000.gpu: RTKit: Initializing (protocol version 12)
  aurora 2300000000.gpu: M5 primary initdata acknowledged
  aurora 2300000000.gpu: M5 secondary initdata acknowledged
  aurora 2300000000.gpu: M5 firmware opening records retired
  [drm] Initialized aurora 1.0.0 for 2300000000.gpu on minor 1

with no coprocessor crash, SError, DART or UAT fault for the minutes
the system ran, and later through a 25-minute desktop session on the
GPU with no GPU errors. That shows the firmware accepting a graph
built from these layouts; it does not confirm any single value. Not
exercised: the 27.2 firmware on hardware, the forced-idle sleep path,
the policy controller words (that board wrote no controller defaults),
the M5 Max and M5 Ultra on 27.2+.

Signed-off-by: Rolando Trevino <rolotrealanis@gmail.com>
Assisted-by: LLM Claude
…14/K116

Applies on top of aurora-silicon/linux PR aurora-silicon#1173.

The 16-inch M5 Pro OLED (K116s, Mac17,12) restores from
UniversalMac_27.2_26B8125_Restore.ipsw, not from the 26B123 image of the
Mac17,8 that aurora-silicon#1173 pins. Its Firmware/agx/armfw_g17x.im4p and
armfw1_g17x.im4p carry a010 (G17S) images whose LC_UUIDs are the uuid of
the K116s ADT's iop-gfx-nub and iop-gfx1-nub (8A2891FC-D479-37E8-895D-
71B4D88ECB51, 58FF964E-F74B-31C2-8179-3837D6ADA9C2), so this is what iBoot
loads. TEXT 0x50000 + 0x54000, DATA 0x184000, the GKTS/ECAP records and
the _rtk_tunables/_rtk_patchbay sections at 26B123's offsets, but the
fwid digest differs:

  26B8125 G17S  af68d034a3f006b43dab661b825f12598cb86e4d2a0e3844f14fa5059f38f6cb
  26B123  G17S  2b4613c62a8a007f22a94101702c9ac6c4e90f2e123f3b36fbe6ffea913f0fd9

(check_fwid.py's algorithm.) Without this
entry the driver refuses the K116s firmware before any GPU write.

It names V26B123_M5: the AGX kext of the 26B8125 kernelcache builds root
version word 0x0c8e_4339_8728_04c0 and its u64[24] allocation size table
is ABI_ALLOCATION_SIZES_26B123_M5 entry for entry (HW data 0x2850, policy
0x12728, status config 0x790), and both firmware roles build the same
version word. The interior
offsets of the policy and the status config were not compared against
26B123's and no 27.2 firmware has run this graph on hardware.

Signed-off-by: Jens Axboe <axboe@kernel.dk>
@sithglan
sithglan force-pushed the thomas/k116s-gpu-26b8125 branch from fc0abd9 to 4ac2c69 Compare November 12, 2026 14:30
sithglan added a commit to sithglan/aura that referenced this pull request Nov 13, 2026
The G17S hand-off admits one firmware build, 26A428 (27.0). On a K116s
(Mac17,12, 16-inch M5 Pro) booted from a 27.2 stub, iBoot loads the a010
images of the K114/K116 restore image, 26B8125, so t6050_gpu_check()
returns 1 and the GPU stays disabled. 26B8125 has 26A428's TEXT and DATA
sizes and records, but its boot-filled ranges are not 26A428's: the
entropy records sit 0x44 (primary) and 0x14 (secondary) bytes further in.

Make the build a table of boot-filled ranges and digest, and add
26B8125 with the values of Linux's drivers/gpu/drm/asahi/hw/t6050.rs
entry for it: commit 4ac2c69dd0b8 ("drm/asahi: t6050: identify the 27.2
(26B8125) G17S firmware of the K114/K116") by Jens Axboe, in
aurora-silicon/linux#1650 on top of #1173 (d8ca53c82e52); digest
af68d034...9f38f6cb. As for 26A428, each role's GKTS and ECAP entropy
bytes lie inside these ranges, so zeroing the ranges gives the digest of
Linux's fwid rule.

The enable line now names the build that matched ("FDT: GPU: T6050 G17S
26B8125 enabled, fw-text at ..."), so a boot log shows which entry
admitted the firmware.

Jens's own hand-off (on aura-internal) enables the GPU without checking
the build; booted by it, the kernel driver identifies 26B8125 and
initialises, and Vulkan and Plasma run on the GPU. This check itself has
not run on a K116s yet.

Signed-off-by: Thomas Glanzmann <thomas@glanzmann.de>
@chrisohearn

Copy link
Copy Markdown

Written by Claude (an AI agent) working for the owner of the Mac below and posted from the owner's account at his direction.

A K114s data point for the K114/K116 27.2 (26B8125) G17S firmware this PR identifies. Board: MacBook Pro 14-inch, M5 Pro (K114s, Mac17,13), G17S B1, firmware 26B8125, kernel 7.3.0-17 plus our patches, mesa-aurora 26.3.0_devel.20261109.j714s2.

Seen on hardware, read by the agent:

  • The GPU runs (Hyprland on the render node, Mesa GLES 3.2). The mailbox interrupt arrives at an idle rate in the hundreds per second.
  • vulkaninfo enumerates one Vulkan 1.4.363 device (driver Borealis, conformanceVersion 0.0.0.0) with a graphics+compute queue family and VK_KHR_wayland_surface.
  • agx_stats reports pstate, requested and achieved frequency, power_mw and temperature_raw as unsupported, and power/runtime_status reads unsupported.

Questions:

  1. Is G17S power and DVFS reporting planned with the 27.2 InitData work in drm/asahi: M5: InitData for the macOS 27.2 and 27.3 firmware (G17S bring-up on J716s) #1173? We can test a branch on the K114s.
  2. Could you share the vkcube setup and the Mesa build and flags used in the K116s run, so we can compare on the K114s?

🤖 Generated with Claude Code

@axboe

axboe commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

@chrisohearn on your second question, the K116s run was nothing special:

  • Mesa: aurora-silicon/mesa aurora-wip at 7f7a7ffa76bb, built as Debian packages with Debian's stock Mesa packaging (release build, no extra options). At the time it needed ASAHI_M5_BRINGUP=1 in the environment; since mesa usb: typec: tipd: cd321x: don't race the resume read in the IRQ test #348 that is gone. I now run plain aurora-wip (1e6f14ca) the same way.
  • vkcube: Debian's vulkan-tools (1.4.341), run with no arguments from a Plasma Wayland session, KWin compositing on the same render node.

For comparison with your agx_stats, on the K116s today (integration/aurora c33c5fd plus #1173 and this PR): pstate_status valid, pstate 0, requested_frequency_hz, power_mw and temperature_raw unsupported, power/runtime_status unsupported. So the same picture on power and DVFS reporting; I'll leave your first question to the series' authors.

Keep the imported M5 firmware layouts and select their Graph through the current board graph path. Preserve common-26 J813 encodings and submission-history caching while relocating the 27.2 history fields.

Signed-off-by: Thomas Glanzmann <thomas@glanzmann.de>
Integration now carries the J813's macOS 27.2 InitData (b70bc80,
through aurora-silicon#2135): RootProfile::J873G18G26B123 and the 26B123 common-interface
layouts. This branch has aurora-silicon#1173's M5 profiles J714G17S26B123 and
J714G17S26C5035 in the same matches. The resolution keeps both: every
match covers all seven profiles, aurora-silicon#1173's m5_layout() early returns stay,
and the 26B123 common-interface arms are integration's. No original
commit is rewritten.

Signed-off-by: Thomas Glanzmann <thomas@glanzmann.de>
@sithglan

Copy link
Copy Markdown
Contributor Author

Refreshed: merged integration/aurora 0abc2f3. The branch is now 2dd5095 (was c6abd0b); no original commit is rewritten.

@chrisohearn on your first question: not in this PR. It only adds the K114/K116 26B8125 firmware identity. Power and DVFS reporting for G17S would come with the InitData and power-policy work, and #1173 is @rolotrealanis98's, so he is the one to say whether it's planned there. axboe's K116s agx_stats above shows the same picture as yours.

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.

4 participants