#
#asahi-dev · 2026-08-01 22:01
yukaSent one remaining design question regarding it to the ML. If you have any thoughts on it, please reply there to keep the context on list: https://lore.kernel.org/asahi/03eb4c22-045e-470e-8259-ebf9b1cfe2ed@cyberchaos.dev/T/#u
#asahi-dev · 2026-08-01 21:59
yukaI communicated with IntegralPilot that I will try to send out the next version of the mtp keyboard series, since he is short on time
#asahi-dev · 2026-08-01 21:42
yukasent
#asahi-dev · 2026-08-01 21:16
svenso maybe send it out soon if you want it in this cycle :-)
#asahi-dev · 2026-08-01 21:15
svenso two more weeks only actually
#asahi-dev · 2026-08-01 21:15
jannauyes
#asahi-dev · 2026-08-01 21:15
svenwait... we're at -rc5 already and almost -rc6, aren't we?
#asahi-dev · 2026-08-01 21:15
sveni'll only be able to pick up the series once the pinctrl thing is in, but i think there's another three weeks until the merge window opens and i usually try to send our pull requests out the weekend before that
#asahi-dev · 2026-08-01 21:13
jannauyou can pick the watchdog and pinctrl dt-binding changes from -next, add them as patch-id dependencies and keep it before the b4 cover letter commit
#asahi-dev · 2026-08-01 21:13
yukaack
#asahi-dev · 2026-08-01 21:12
jannaudepend on it
#asahi-dev · 2026-08-01 21:12
svenyeah, please mention it in the cover letter and the patch
#asahi-dev · 2026-08-01 21:12
jannauplease mention that in the cover letter, possible also as not in the individual commit below `--- `
#asahi-dev · 2026-08-01 21:12
yukabut that's really the question. my change touches the same file as the m3 pro/max one which was already appplied in pinctrl, and I can make my patch either depend on that, or conflict with that.
#asahi-dev · 2026-08-01 21:11
yukaOr that
#asahi-dev · 2026-08-01 21:11
sveni expect the pinctrl people to pick up the the pinctrl change again
#asahi-dev · 2026-08-01 21:10
svenwhy?
#asahi-dev · 2026-08-01 21:07
yukaAnd then, whoever merges apple-soc will have to resolve conflicts with pinctrl
#asahi-dev · 2026-08-01 21:06
svenplease use apple-soc as base so that i don't get merge conflicts when trying to merge it
#asahi-dev · 2026-08-01 20:57
yukaThe alternatives would be linux-next as base-commit and only the M3 Pro/Max v3 as additional dependency, or apple-soc as base and the two dt-bindings commits as dependencies
#asahi-dev · 2026-08-01 20:55
yukaSo I use 7.2-rc5 as base-commit and then add the two dt-bindings and M3 Pro/Max v3 as additional dependencies?
#asahi-dev · 2026-08-01 20:40
jannauhttps://b4.docs.kernel.org/en/latest/contributor/prep.html#working-with-series-dependencies
#asahi-dev · 2026-08-01 20:38
yukaI will look into that, thanks
#asahi-dev · 2026-08-01 20:37
jannaut603x changes won't be in next until next week, but apple-soc misses 2 dt-binding changes (pinctrl and watchdog). With b4 you should be able to butcher a tree together and annotate the dependencies
#asahi-dev · 2026-08-01 20:31
yukashould I base apple-m4-initial-devicetrees v2 on linux-next or apple-soc?
#asahi-dev · 2026-08-01 20:09
jannauhmm, m3 ultra might not be actually two m3 max (at least not the same m3 max as used for macbooks) due to the thunderbolt 5 support
#asahi-dev · 2026-08-01 19:33
jannaudone, quite a lot of updates: https://github.com/AsahiLinux/docs/pull/275
#asahi-dev · 2026-08-01 18:49
svenokay, re-pushed
#asahi-dev · 2026-08-01 18:47
sven*:(
#asahi-dev · 2026-08-01 18:47
svenprobably forgot -s :*
#asahi-dev · 2026-08-01 18:46
sven*Sigh*
#asahi-dev · 2026-08-01 18:46
svenah crap, why didn't b4 add my sob to that series
#asahi-dev · 2026-08-01 18:45
svencertainly didn't
#asahi-dev · 2026-08-01 18:41
jannauI guess nobody kept really track of the feature support since it moved off the wiki? mostly asking for M3*
#asahi-dev · 2026-08-01 18:40
jannausven: thanks
#asahi-dev · 2026-08-01 18:17
svenjannau: okay, just applied the m3 series
#asahi-dev · 2026-08-01 16:58
amarioguymakes this cursed hack easier at least...
#asahi-dev · 2026-08-01 16:58
amarioguygotcha, thanks!
#asahi-dev · 2026-08-01 16:58
yuka"u.cpu_features.apple_sysregs_unlocked"
#asahi-dev · 2026-08-01 16:57
yukaAnd that's also integrated into the proxyclient utils
#asahi-dev · 2026-08-01 16:57
amarioguyah yep
#asahi-dev · 2026-08-01 16:57
yukaisn't that just cpu_features->apple_sysregs_unlocked?
#asahi-dev · 2026-08-01 16:57
amarioguysorta came to mind because the soc list for checking that stuff is only going to get larger
#asahi-dev · 2026-08-01 16:55
amarioguysort of an rfc but thoughts on adding a func to m1n1 that returns a bool for if the soc has impdef stuff disabled in raw boot mode?
#asahi-dev · 2026-08-01 11:43
biosedWorth it on this hardware: the same monitor's native mode over HDMI is 545 MHz pixel clock and is always blank (anything above ~390 MHz fails here), and Huawei caps HDMI at 50 Hz at native res anyway. DP altmode is the only path to native 60.
#asahi-dev · 2026-08-01 11:43
biosedToolchain note: rustc 1.95.0 + bindgen 0.72.1 both passed 'make rustavailable' and built clean - docs list 1.85.0 / 0.71.1 as minimums, so newer works fine here.
#asahi-dev · 2026-08-01 11:43
biosedfairydust @ e3e35907c17a (base 7.1.5) on Fedora Asahi Remix 44. Result: DP-1 connected, 3840x2560@59.98 native over typec1/atcphy1 on a Huawei MateView 28.2" (3:2 panel). Internal panel unaffected, still 3024x1890@120.
#asahi-dev · 2026-08-01 11:43
biosedDatapoint: fairydust DP altmode confirmed working on j314s (MBP14 M1 Pro, t6000).
#asahi-dev · 2026-08-01 10:00
jannauhttps://github.com/AsahiLinux/m1n1/pull/645
#asahi-dev · 2026-08-01 09:55
jannauI'll sent fix after testing

plus ›