#asahi-dev · 2026-01-02 00:58
integralpilotbtw, just figured out how to patch the issue with charge_behaviour for the driver for M3 SMC (or updated M1/M2 firmware): it's a new key called CHTE. testing it now#asahi-dev · 2026-01-02 00:57
integralpilotoh no that's annoying! hopefully we can get it working on M3 Max too with a bit of RE#asahi-dev · 2026-01-01 12:07
integralpilotonly have M3 so can’t see how it’s changed#asahi-dev · 2026-01-01 12:06
integralpilotdebugging a tricky NVMe issue now, and if anyone could send the NVMe trace (from start of trace till to first nvme_cmd_read) on M1 or M2 under hypervised XNU and hypervised Linux I would appreciate it a lot!#asahi-dev · 2026-01-01 10:50
integralpilotI’m not sure it really works though cause I’ve used it once to ask them to upload a KDK for a release they forgot to do it for and now that’s not even the current release and still no KDK#asahi-dev · 2026-01-01 10:50
integralpilotoh interesting, that’s weird!#asahi-dev · 2026-01-01 10:31
integralpilotI can’t imagine the reason it does that though? Maybe they use some standard deserialisation thing that defaults to decimal probably#asahi-dev · 2026-01-01 10:29
integralpilottempted to open feedback assistant (they accept developer tools feedback) and put something about the ioreg memory addresses being in DECIMAL not hex cause it’s annoying but I doubt they’d actually change it#asahi-dev · 2026-01-01 07:28
integralpilotlooks really cool! :)#asahi-dev · 2025-12-31 08:12
integralpilotanyway sorry for boring you guys with x86 RE!#asahi-dev · 2025-12-31 08:09
integralpilottaped out CLKREQ# and WAKE# too and still no luck, guess it's happening at the link training level :(#asahi-dev · 2025-12-31 07:34
integralpilotand i thought apple hardware was frustating at a low level lol...#asahi-dev · 2025-12-31 07:34
integralpilotmy 2015 BIOS (even updated it to the 2017 version but didn't fix) refuses to POST with the PCIe to M.2. adapter i got so now i need to physically tape over the SMBus pins and hope it works lol. :(#asahi-dev · 2025-12-31 07:00
integralpilotbacked up most things, just the linux kernel folder with DTs and RTKit got ignored my by backup service cause it was too big (cause build artifacts etc.)#asahi-dev · 2025-12-31 06:40
integralpilotit lasted a while though, it's from 2012 and was originally used in a CCTV DVR before i got it second ahnd, just shows how durable WD Golds are i guess#asahi-dev · 2025-12-31 06:35
integralpilot*took#asahi-dev · 2025-12-31 06:35
integralpilotthankfully i look notes in a physical journal so should be able to re-create it all easily once i get the my new SSD i got and new distro etc. setup#asahi-dev · 2025-12-31 06:34
integralpilotmy hard drive died this morning and took my in-progress RTKit/ascwrap/NVMe work and t8122 and t6030 device trees with it :<#asahi-dev · 2025-12-31 01:18
integralpilotwell i mean that's expected, you need to be able to talk to coprocessors to do almost anything - NVMe, trackpad etc. #asahi-dev · 2025-12-30 11:00
integralpilotstill says 12, but it's sending oslog messages that the previous driver didn't know how to handle and said were an invalid format#asahi-dev · 2025-12-30 10:55
integralpilotperfect, thanks!#asahi-dev · 2025-12-30 10:52
integralpilotthank you, makes sense!#asahi-dev · 2025-12-30 10:51
integralpilotthanks! so is it better to wait untill all of rtkit is ready for M3 and submit a series, or submit oslog now? and i shouldn't make a PR to asahi?#asahi-dev · 2025-12-30 10:46
integralpilotthere's definetely still more RTKit fixing to do but i feel like smaller, self-contained patches are better than just once big "RTKit M3 makeover" patch but not sure about upstream dynamics or when we should send stuff there#asahi-dev · 2025-12-30 10:45
integralpilotgiven RTKit is also in mainline, once merged into asahi, should i bring this oslog patch upstream as well?#asahi-dev · 2025-12-30 10:44
integralpilotuploading PR soon just doing some testing#asahi-dev · 2025-12-30 10:44
integralpilotjust finished RE of new RTKit oslog message format, the updated driver is working now#asahi-dev · 2025-12-30 09:55
integralpilotoh interesting, thank you!#asahi-dev · 2025-12-30 09:54
integralpiloti thought on normal macOS boot there's nothing in EL2, but maybe i'm wrong#asahi-dev · 2025-12-30 09:52
integralpilotit's annoying that it doesn't like trap to us in EL2 when EL1 touches these, it sends an exception to El1 and doesn't notify us#asahi-dev · 2025-12-30 09:51
integralpilotto my knowledge there's no way for us in EL2 to allow EL1 to access these, so we have to binary patch, but there might be another way#asahi-dev · 2025-12-30 09:51
integralpilotwhich i guess makes sense for them to be protected like this, probably if you are a hypervisor running a sandboxed VM, you don't want it messing with sensitive registers like that#asahi-dev · 2025-12-30 09:50
integralpilotif we don't set the chickens, XNU hangs at some sha512 function, so i assume they are crypto related in some way#asahi-dev · 2025-12-30 09:49
integralpilotthey seem to be registers which, when there is nothing in EL2, access it allowed from EL1. but when there is something (m1n1) in EL2, EL1 is not allowed to touch them#asahi-dev · 2025-12-30 09:47
integralpilotjinx#asahi-dev · 2025-12-30 09:47
integralpilot#asahi-stream ?#asahi-dev · 2025-12-30 09:45
integralpilotwell i guess it's more intended as like techno background music while it shows the schedule and stuff as they set up#asahi-dev · 2025-12-30 09:44
integralpilotlol#asahi-dev · 2025-12-30 09:44
integralpilotwhy is it like ominous video game boss music#asahi-dev · 2025-12-30 09:42
integralpilotoh, makes sense#asahi-dev · 2025-12-30 09:41
integralpilotthere's no sound :(#asahi-dev · 2025-12-30 09:08
integralpilotsven: good luck with your talk! it starts in about an hour right? i'm sure it will go amazing!#asahi-dev · 2025-12-29 13:31
integralpilotyou will probably need to make some modifications for your specific board (J-number) if it's different, though#asahi-dev · 2025-12-29 13:31
integralpiloti do, i can send through in the morning if you'd like as it's late here now and i probably need to log off!#asahi-dev · 2025-12-29 13:29
integralpilotoh, sorry if i misunderstood Shiz! no m1n1 changes needed for linux boot (some very smart people have already gotten it working on M3 for us!), just mainly a devicetree. i can send you an example of mine for my devices right now or help you write yours (if you send over some data). #asahi-dev · 2025-12-29 13:24
integralpilotsure! i'll try tomorrow, i'll make it update the chicken bits and apply the binary patches automatically if you use a command line flag, but they aren't fully ready yet as it doesn't boot all the way due to an issue and i still want to investigate the chickens a bit more (i have now deduced that they are crypto/SHA512 related, i think). for now, if you'd like to try you can use the gist instructions (https://gist.github.c#asahi-dev · 2025-12-29 12:13
integralpilotoh thanks! i've fixed it now#asahi-dev · 2025-12-29 12:08
integralpilotfor some reason the CI sign-off verifying job failed even though i did sign it off?#asahi-dev · 2025-12-29 12:08
integralpilotPR live now: https://github.com/AsahiLinux/linux/pull/432#asahi-dev · 2025-12-29 12:08
integralpilotthanks!