#
#asahi-dev · 2026-01-04 14:54
nickchanI have some patches for soc/apple on the list
#asahi-dev · 2026-01-04 10:53
maz+1.
#asahi-dev · 2026-01-04 10:53
sveni much prefer to finally work on tbt and pcie hotplug
#asahi-dev · 2026-01-04 10:53
svenyup
#asahi-dev · 2026-01-04 10:52
mazat this point, the onus is on the x86 folks to do the work.
#asahi-dev · 2026-01-04 10:49
svenwhich works, but i was too lazy to do all that especially since I don't have any t2 machines to test :D
#asahi-dev · 2026-01-04 10:49
sveni think his suggestion was to move the apple silicon backend to drivers/soc/apple and the x86 backend to some other place
#asahi-dev · 2026-01-04 10:48
chadmedwell we can start an "i told you so" tab
#asahi-dev · 2026-01-04 10:48
chadmedoh yeah we ripped out the fe/be abstraction too
#asahi-dev · 2026-01-04 10:47
svenhaven't heard from the t2 people in a long while either, they wanted to add support for their chips at some point as well
#asahi-dev · 2026-01-04 10:46
chadmedand we only managed to get the core merged by pinky promising that it wouldnt get (much) bigger
#asahi-dev · 2026-01-04 10:46
chadmedyeah they were originally in the core
#asahi-dev · 2026-01-04 10:44
integralpilotoh, i guess we keep them seperate then
#asahi-dev · 2026-01-04 10:44
sventhe mfd maintainer didn't like those inside drives/mfd in the original submission fwiw
#asahi-dev · 2026-01-04 10:42
integralpilotchadmed: since in both our patches we define internal f32 helpers (i think you do this in hwmon), after they both make linux-next do we want to make a refactor patch to move all f32 helpers to the main smc code to avoid duplication (it might be hard to coordinate this prior to linux-next as they go through different maintainer trees)?
#asahi-dev · 2026-01-04 10:41
integralpilotgood luck, thanks for the work you do!
#asahi-dev · 2026-01-04 10:34
svenI have to catch up on reviewing and merging things for our tree as well
#asahi-dev · 2026-01-04 10:33
svenusually quicker than having to send another revision via email 🫠
#asahi-dev · 2026-01-04 10:33
svenfeel free to mention the branch here once you’re done, I usually do the same and people then catch small issues to be fixed before submitting
#asahi-dev · 2026-01-04 10:33
chadmedi have to resend the other smc series too
#asahi-dev · 2026-01-04 10:32
svennice!
#asahi-dev · 2026-01-04 08:16
integralpilotmacsmc-power refactoring and updates for new firmware going well, almost ready for upstream i think
#asahi-dev · 2026-01-04 04:48
nickchanso likely what happened there is EL1's m1n1 tries to set the _EL12 register which of course explodes
#asahi-dev · 2026-01-04 04:45
nickchanthis is completely disregarding NV which is not a rabbit hole i want anyone to go into
#asahi-dev · 2026-01-04 04:41
nickchanso all the standard ARM VHE caveats but applied to a custom register
#asahi-dev · 2026-01-04 04:40
nickchanlikely other bits in the register will make EL0 24/1GHz and it might depend on HCR_EL2.TGE from how things are going
#asahi-dev · 2026-01-04 04:39
nickchanthis is vhe stuff
#asahi-dev · 2026-01-04 04:38
nickchanfyi AGTCNTRDIR_EL2 = s3_4_c15_c14_5
#asahi-dev · 2026-01-04 04:37
nickchannot sure about EL0 you should play around with the bits in the registers
#asahi-dev · 2026-01-04 04:36
nickchanand the second one would only work in EL2
#asahi-dev · 2026-01-04 04:36
nickchanso i think the first chicken sets ${CurrentEL}'s arch timer to 24 MHz (redirect to apple timer as discovered in xnu source code) and the second one sets EL1 arch timer to 24 MHz from EL2
#asahi-dev · 2026-01-04 04:35
nickchanfl0_id: about the chickens s3_1_c15_c1_5 appears to be AGTCNTRDIR_EL1, and s3_4_c15_c14_6 appears to be AGTCNTRDIR_EL12
#asahi-dev · 2026-01-04 03:39
rosalyntg_(as well as similar treatment for the mux-controls)
#asahi-dev · 2026-01-04 03:34
rosalyntg_Am I correct in thinking the correct way to get both USB-C ports working with DP-altmode is dropping the apple,dptx-phy, adding both phys to the dcpext, then calling dptxport_connect after a DP altmode has been negotiated on the correct phy? I'd be interested in taking that on if nobody is already working on it....
#asahi-dev · 2026-01-04 01:00
fl0_id_https://www.pastery.net/hruxye/
#asahi-dev · 2026-01-04 01:00
fl0_id_integralpilot ok, I get some output on ACM1. but yeah it looks like only m1n1 output
#asahi-dev · 2026-01-04 00:35
integralpilotAsahi logo with logs is EL1 m1n1, can’t be sure if it’s loaded the kernel yet unless you monitor /dev/ttyACM1 in picocom which is where EL1 m1n1 will send you its logs
#asahi-dev · 2026-01-04 00:28
fl0_id_to clarify for integralpilot - it briefly shows the rainbow logo, then switches to asahi logo with logs (which I assume is the kernel) but only very briefly, before reloading m1n1
#asahi-dev · 2026-01-04 00:14
fl0_idbut I'll try again to be sure
#asahi-dev · 2026-01-04 00:14
fl0_idintegralpilot i think I tried only rootwait or no args already
#asahi-dev · 2026-01-04 00:13
integralpilot(sorry pressed enter too soon)
#asahi-dev · 2026-01-04 00:13
integralpilotalpine rootfs if you’d like and we can see if it works
#asahi-dev · 2026-01-04 00:13
integralpilotthen I will send my
#asahi-dev · 2026-01-04 00:13
integralpilotjust out of curiosity, could you try no boot args, just “”. i remember earlycon was causing some problems for me earlier. Ideally it boots to a panic on framebuffer about no rootfs
#asahi-dev · 2026-01-03 23:54
fl0_id*know
#asahi-dev · 2026-01-03 23:54
fl0_idif they kno
#asahi-dev · 2026-01-03 23:54
fl0_idcan we ask dberlin what those two first chickens for t6031 were for?
#asahi-dev · 2026-01-03 23:53
fl0_idI'll make a video to be sure...
#asahi-dev · 2026-01-03 23:53
fl0_idmmh EL1 m1n1... I think so?
#asahi-dev · 2026-01-03 23:52
fl0_idthe chainloaded m1n1 loaded for sure.

plus ›