#
#asahi-dev · 2026-09-24 18:37
jannau`ioreg -l | grep chip-id` from a M5 Max / Ultra should clear things up
#asahi-dev · 2026-09-24 18:35
jannaum5 ultra has "clpc,t6050d", dispext has "dispext0,t605x"
#asahi-dev · 2026-09-24 18:33
jannauI would expect the combination of cpu and base tile to have each their own chip-id, 27.0 Devicetrees from the ipsw have 0 as chip-id
#asahi-dev · 2026-09-24 18:32
chaos_princesslet's just do t6051 for consistency and hope that apple does not release something that conflicts with that number
#asahi-dev · 2026-09-24 18:31
yukaI don't remember
#asahi-dev · 2026-09-24 18:31
yukabut possibly same chip id
#asahi-dev · 2026-09-24 18:31
yukaM5 Pro and M5 Max cores definitely have different MIDR part numbers
#asahi-dev · 2026-09-24 18:27
mmediouni[m]CPU tile is the same though
#asahi-dev · 2026-09-24 18:27
mmediouni[m]M5 Pro and Max are different tapeouts for the base tile that contains dram controllers and GPU
#asahi-dev · 2026-09-24 18:21
jannaum5 ultra has the same chip_id as max? this sounds unexpected. I would have also expected that M5 Pro and Max have different chip_ids
#asahi-dev · 2026-09-24 18:19
yukaHmm okay
#asahi-dev · 2026-09-24 18:19
nickchant6051 doesn't seem to exist
#asahi-dev · 2026-09-24 18:18
jannau m1 max has only 'compatible = [pmgr1,t6001]'. it's based on the chip_id
#asahi-dev · 2026-09-24 18:18
nickchanm5 max and m5 ultra is chip id 0x6050
#asahi-dev · 2026-09-24 18:16
yukaah but this was already the case for M3 Ultra for example
#asahi-dev · 2026-09-24 18:16
yuka> do I call the M5 Max SoC t6051? there is no single mention of t6051 in an M5 Max adt
#asahi-dev · 2026-09-24 18:02
Overtone[m]just sayin. new to topic and dont know too much.
#asahi-dev · 2026-09-24 18:01
Overtone[m]Is it that important to call it what Apple arbitrary calls it inside the company instad of just saying the public known name?
#asahi-dev · 2026-09-24 18:00
yukaBut I think it did have a different chip id?
#asahi-dev · 2026-09-24 17:59
yukado I call the M5 Max SoC t6051? there is no single mention of t6051 in an M5 Max adt
#asahi-dev · 2026-09-24 17:58
yukaAhh
#asahi-dev · 2026-09-24 17:56
Overtone[m]Hello
#asahi-dev · 2026-09-24 16:45
yukaLiterally the M4 Pro Mac mini (j773s) has compatible = [arm-io,t6041]
#asahi-dev · 2026-09-24 16:44
yukado we follow apple's odd naming of t6041 (not t6040) for t604x base compatibles?
#asahi-dev · 2026-09-24 16:16
svenworks for me
#asahi-dev · 2026-09-24 16:15
yukalet's close the m1n1 PR as well then, since jannau and you are both slightly against it?
#asahi-dev · 2026-09-24 16:15
yukaack
#asahi-dev · 2026-09-24 16:15
sveni'm not a big fan on the m1n1 refactor tbh, i'd just copy/paste
#asahi-dev · 2026-09-24 16:14
yukaIt's the same thing as in m1n1, the code is almost the same except different offsets
#asahi-dev · 2026-09-24 16:14
yuka*would you prefer
#asahi-dev · 2026-09-24 16:14
yukasven: for SARTv4 support in Linux, would you a refactor or just copy, paste and adjust the sartv3 defines and functions?
#asahi-dev · 2026-09-24 15:03
myriaThough not sure I want the affinities to be an array, there will be too many spaces for it to be an efficient use of memory
#asahi-dev · 2026-09-24 15:03
myriaSame with m6, so it might just be a case of M3 table, then M4/5/6 tables
#asahi-dev · 2026-09-24 15:02
myrianickchan: Yeah, the cpu tables are definitely different. And I think M3/M4 are different, but M5 seems to just be extra events on top of m4
#asahi-dev · 2026-09-24 14:40
jannau80 char line length moved to --mode stricter in next
#asahi-dev · 2026-09-24 14:36
jannauwas the not exactly aligned strict check dropped? it sounds like that would conflict with mixed-indent-chars
#asahi-dev · 2026-09-24 14:23
yukabut might need to stop properly aligning the properties with line breaks in the next device trees since that's not really universally possible with tabs-only
#asahi-dev · 2026-09-24 14:21
yukaI dislike it
#asahi-dev · 2026-09-24 14:21
yukawhich is not even strict-only
#asahi-dev · 2026-09-24 14:21
yukaAlso, they newly added a mixed-indent-chars?
#asahi-dev · 2026-09-24 14:20
svenlet’s maybe hold off on strict warnings then
#asahi-dev · 2026-09-24 14:20
sven🙃
#asahi-dev · 2026-09-24 14:20
yukaso depending on which branch I'm working on, I get errors or not
#asahi-dev · 2026-09-24 14:20
yukaI think the dt-check-style ordering requirements have changed in linux-next, model and compatible are now the other way around /o\
#asahi-dev · 2026-09-24 14:08
linkmauvendufresne, did that Freerunner driver ever get mainlined btw? I took mine out a few years ago and was pretty disappointed I still had to use a 2.6.3x kernel…
#asahi-dev · 2026-09-24 13:58
yukano I just wanted to test it
#asahi-dev · 2026-09-24 13:58
yukano worries
#asahi-dev · 2026-09-24 13:56
integralpilotunless you have anything you'd like changed
#asahi-dev · 2026-09-24 13:56
integralpilotand then list (along with BRCM4388 v1) tomorrow evening
#asahi-dev · 2026-09-24 13:55
integralpilot(to GH)

plus ›