2026-06-15
00:15hdbngr has joined #asahi-dev
00:24hdbngr has quit [Ping timeout: 480 seconds]
00:55ipatch_ has joined #asahi-dev
00:55ipatch has quit [Read error: Connection reset by peer]
01:38kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
01:40jnn has joined #asahi-dev
01:43jn has quit [Ping timeout: 480 seconds]
01:44freetolga has joined #asahi-dev
01:45steinsgate has quit [Quit: Connection closed for inactivity]
01:58marvin24 has quit [Ping timeout: 480 seconds]
02:00yurix has quit [Remote host closed the connection]
02:00yurix has joined #asahi-dev
02:35tobhe has joined #asahi-dev
02:41xal_ has joined #asahi-dev
02:42tobhe_ has quit [Ping timeout: 480 seconds]
02:43xal has quit [Read error: Connection reset by peer]
02:56kaleryeblueberryoboe has joined #asahi-dev
03:20webeshadjkaksd[m] has joined #asahi-dev
03:36nora_ has joined #asahi-dev
03:38nora has quit [Ping timeout: 480 seconds]
03:43marvin24 has joined #asahi-dev
04:23kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
04:25kaleryeblueberryoboe has joined #asahi-dev
04:34ddxtanx_ has joined #asahi-dev
04:34ddxtanx has quit [Read error: Connection reset by peer]
04:57hdbngr has joined #asahi-dev
05:11hdbngr has quit [Ping timeout: 480 seconds]
05:24hdbngr has joined #asahi-dev
05:36hdbngr has quit [Ping timeout: 480 seconds]
05:39chadmed has quit [Quit: Konversation terminated!]
05:39chadmed has joined #asahi-dev
05:40hdbngr has joined #asahi-dev
05:48hdbngr has quit [Ping timeout: 480 seconds]
06:19mattia013 has joined #asahi-dev
06:23ipatch_ has quit [Ping timeout: 480 seconds]
06:27hdbngr has joined #asahi-dev
06:38hdbngr has quit [Ping timeout: 480 seconds]
06:43kaleryeblueberryoboe has quit [Remote host closed the connection]
07:04jnn is now known as jn
07:12chadmedlet me be more specific, i wonder how many ultra-equipped studios they actually sell to people who arent ai hypebeasts
07:12nickchani really think most people that bought the high ram ultras are doing ai inference of sorts
07:13jannauchadmed: I'm unhappy that only forced VRR works. I'd prefer if the driver at least worked with a compositor which can deal with the needs_modeset to enable VRR
07:13nickchanthe kind of demand good for those ultra would need to require loads of VRAM, but not fast VRAM
07:15chadmedjannau: fair enough. ill ask xaver again but iirc the consensus was "lets wait and see what the drm maintainers decide to do about the hdmi spec"
07:16chadmedi'll finish off HDR and surface handling separately, because i do want to pick up oliver's work on compression too (if he doesnt come back ~soonish)
07:16nickchanthe m2 ultra has 24 cpu so it looks like not even apple is escaping their own 2 VM limit
07:17chadmedi know, but are there any compositors that currently allow vrr toggling with a full modeset?
07:17chadmedif kwin folks want to wait for drm to make a decision then we are kind of at the mercy of that anyway
07:21nickchanseems like some recent T2 firmware have the SMC gain enough keys to "support" the macsmc-battery driver which is not something I want to support because half of the keys ar
07:21chadmedchaos_princess: are you reasonably confident that the M3 device audio configs dont need any changes? i'll tag asahi-audio and the ucm conf stuff if so and add some comments to macaudio for the of match table
07:22chadmed(im mostly concerned about the speakersafetyd parameters, as long as we dont melt anyones tweeters im happy for now)
07:22jannauI fear VRR is in anycase a lost cause on apple. xaver is also waiting on controls for min/max refresh for VRR. As far as I see we can't control that either without modeset
07:24nickchani feel like for cpu if some sysreg workaround ugly enough is posted on the list then the people at Arm Limited may bother apple to unlock them and that could be much faster
07:25hdbngr has joined #asahi-dev
07:25JamesCalligeros[m]There is a possible nightmare ending scenario to that too
07:26sveni think file feedback report -> forward FBxxx number to some apple engineer kinda works so no need to try and escalate that to something else
07:27JamesCalligeros[m]Yeah we dont need to pick unnecessary fights
07:28jannauit kinda works. we need to learn to file those earlier instead of wasting time/effort trying to find the issue on our side
07:29svenand if this is regarding wfi: at this point it looks like the "force wfi to use clock gating only" debug settings are just gone in hardware so even filing a feedback report wouldn't really help us
07:30DD65 has joined #asahi-dev
07:32svenyes, but xnu doesn't touch it anymore. there's even a "/* CPU_OVRD register accesses are banned */" comment
07:32nickchanthere's other explainations for that NO_CPU_OVRD, like the job is done by sptm or preconfigured by iBoot
07:34hdbngr has quit [Ping timeout: 480 seconds]
07:35chaos_princesschadmed: for !j504 - yes
07:35svenfrom yesterday: 11:36:17 <sven> fwiw, we essentially got confirmation that wfi losing state on m4+ is expected because that cyc_ovrd thing we set just doesn’t exist anymore
07:36JamesCalligeros[m]Cool, i will sort it all out in a bit then
07:36ddxtanx_ has quit [Remote host closed the connection]
07:37chaos_princessand idk what's up with internal mics. They re-done how the decimator works, so we may or may not need to re-tune them, idk.
07:37JamesCalligeros[m]Well the good news is that theyre not tuned at all currently apart from the gain
07:38chaos_princessi _think_ i am doing the aop part correctly, but admac is not cooperating, and macos is doing something cursed to it that i may or may not need to do too
07:40Sobek[m]<JamesCalligeros[m]> "There is a possible nightmare..." <- Yep, ARM could pressure Apple into locking down the thing more.
07:41hdbngr has joined #asahi-dev
07:42DD65 has quit [Remote host closed the connection]
07:42Sobek[m]sven: Confirmation from the thing https://en.wikipedia.org/wiki/The_Thing_(listening_device) clearly !
07:47DD65 has joined #asahi-dev
07:56hdbngr has quit [Ping timeout: 480 seconds]
07:58chaos_princessis this aud? cause 2k usd for that thing is crazy even new
08:04hdbngr has joined #asahi-dev
08:12ipatch has joined #asahi-dev
08:13hdbngr has quit [Ping timeout: 480 seconds]
08:34chaos_princess has quit [Quit: chaos_princess]
08:34chaos_princess has joined #asahi-dev
08:36hdbngr has joined #asahi-dev
08:41pb17 has quit [Ping timeout: 480 seconds]
08:44pb17 has joined #asahi-dev
08:46hdbngr has quit [Ping timeout: 480 seconds]
08:46nickchanfwiw yuka's patch works well on pre-M1 with cyc_ovrd workaround disabled or force down so I will give R-b when it hits the list
08:48yukaI sent it to the auto detected lists (arm-kernel) yesterday but forgot to add the asahi list
08:51chaos_princessjust fix it in v2
08:51chaos_princessyou can do it, but it is kinda complicated, and if you get it wrong, you annoy everyone
08:53hdbngr has joined #asahi-dev
08:54gargantua has joined #asahi-dev
09:04gargantu1 has joined #asahi-dev
09:06gargantua has quit [Ping timeout: 480 seconds]
09:10chaos_princesscan you run the experiment on m4 in el1 then?
09:10chaos_princessthere is el1_call or sth in m1n1
09:10chaos_princessunder m1n1
09:10chaos_princesswith hcr configured not to trap
09:11kaleryeblueberryoboe has joined #asahi-dev
09:13gargantu1 has quit []
09:14oliverchadmed: please feel free. I am still here and reading. I am using my patches without any issues since month now, but I don't have the time to follow up on that.
09:19kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
09:27kaleryeblueberryoboe has joined #asahi-dev
09:33yukaI can't set my mac os 27 installation to permissive (or even reduced) security on the macbook neo :(
09:34kaleryeblueberryoboe has quit [Remote host closed the connection]
09:35kaleryeblueberryoboe has joined #asahi-dev
09:36chaos_princessdo you have an asahi install, and is your device a laptop
09:37chaos_princessyou don't
09:38chaos_princessah, right
09:38chaos_princessits a bug
09:38chaos_princessi couldn't do csrutil disable on 27 in a vm either with the same error
09:39chaos_princessgeneric linux works
09:39chaos_princessi started with a 2011 intel mbp as the host device running linux
09:40hardy94 has joined #asahi-dev
09:41chadmedthe only reason to have a second apple silicon mac is if you need debug uart via tuxvdmtool
09:41hdbngr has quit [Ping timeout: 480 seconds]
09:50kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
09:51hdbngr has joined #asahi-dev
09:55nickchanactually no, what it doesn't like is frequency starting to decrease when a switch is initiated, only to increase again halfway through the switch
09:55kaleryeblueberryoboe has joined #asahi-dev
09:55yukanickchan: probably the core you're testing is in the same cluster as the boot core which m1n1 is running on
09:56nickchanif switching from one core type to another then the frequency always decrease to around 450 MHz, change MPIDR, and start to increase again
10:00nickchanin my case once the cpu switch to the lower state, it can't keep up with 1.5M baud anymore
10:01yukaAlso 1.5M baud generally does not work on my neo, I always comment out the baudrate switch if I need to use the serial
10:05yukaCentral scrutinizer worked sometimes I think but something else is borked there (it is very unreliable with the Neo)
10:05nickchanin any case it seems i should keep all pre-m1 cpu pstate experiments to myself for longer since none of them work without usb dwc2
10:05jannauchadmed: what do you need j504 for? I'd expect it to be very close to j[3-5]14 audio-wise. I haven't had time yet to look into it
10:07chadmedim not sure why theyd do that given its the same chassis as the others but whatever, its different
10:07chadmedyou can test the 314 config if you want, but thats going to suck regardless because it needs redoing
10:13jannauI'd expect Apple has to do testing anyway to detect unexpected issues due to changes (missing usb-c port, single fan and different main pcb) and then there isn't any reason not to do a proper per device calibration
10:16kaleryeblueberryoboe has quit [Remote host closed the connection]
10:24Sobek[m]chaos_princess: (Btw, it is interesting that the two releases that dropped a whole architecture (Snow Leopard and Golden Gate), are both kind of low on features)
10:26chaos_princessgate does not fully drop an architecture
10:26chaos_princessin order for rosetta2 to work, they still need to compile the entire macos userland for x86
10:26chaos_princessonly kernel bits are gone
10:27Sobek[m]chaos_princess: Snow Leopard had Rosetta 1 too. It's more that they drop support for hardware with that archtiecture. (Host Architecture ?)
10:47jannauspeakers have the same part number but the audio board differs between j504/j514. the latter seems to be just the headphone amp though
10:51chaos_princesscan we even support it? it comes with 15
10:53chadmedit was more for putting in all the places we document the AIDs and configs (speakers.txt and macaudio.c) but i can just leave it out
10:53chaos_princessanyway, give me a few mins, will get the aid
10:58chaos_princessacoustic-id = 33
11:00hdbngr has quit [Ping timeout: 480 seconds]
11:01hdbngr has joined #asahi-dev
11:20chaos_princessCNTHCTL_EL2.EL1PCEN
11:20chaos_princessshould help
11:29chaos_princessopposite
11:29chaos_princess0b1 This control does not cause any instructions to be trapped.
11:31hardy94 has quit [Remote host closed the connection]
11:31chaos_princessalso set EL1PTEN
11:34chadmedokie doke userspace audio components have been tagged/released, couple of trivial kernel patches at https://github.com/AsahiLinux/linux/pull/519
11:35chaos_princessmaybe try using the virtual counter then?
11:38chaos_princessso broken
11:38chaos_princessso kvm will have to trap it
11:40chaos_princessstill only apply in el2, kvm unbreak can be in a different patch
12:29chaos_princessit shouldn't do that anyway
12:29nickchanonly real reliable indicator of running bare metal is checking "apple,arm-platform" in the root node fdt compatible
12:31chaos_princesscan we put a 'wfi-broken' into the cpu dt node or something?
12:31chaos_princessseems better than indirect guesses
12:32fl0id_oftc has joined #asahi-dev
12:50yukait no longer does that because it breaks on M4+, so I introduced an explicit list of hosts to enable it on
12:51chaos_princesscpuidle-apple is not upstream
12:52jannauplease move the main discussion on list. that's more constructive than to confuse people with new revisions every 12 hours
13:06kaleryeblueberryoboe has joined #asahi-dev
13:06svenhm, i don't even remember where "must use pci" came from. maybe during early upstreaming on list? or maybe even on irc
13:06pb17 has quit [Ping timeout: 480 seconds]
13:11chaos_princessthe only thing i can find is "Further, it is essential that the ARMv8 SoC provide a fully functional implementation of PSCI; this will be the only mechanism supported by ACPI to control CPU power state. "
13:11chaos_princesswhich, well, covers acpi, not dt
13:17sveni remember the argument being that they don't want to open the floodgates for N custom cpuidle drivers if they would accept one for apple silicon
13:18chaos_princesscounterargument - we don't have an el3 to hide our sins in
13:20pb17 has joined #asahi-dev
13:21svendo we need callbacks or whatever to other drivers for deep sleep? because that would be very annoying with just psci as well
13:21chaos_princesswell, it is an argument for the list
13:22chaos_princessyou mean the acc_ovrd deep sleep? - unclear, but signs point to yes
13:22chaos_princesslike 'probably have several gpio drivers become proxies to psci' levels of yes
13:24chaos_princessoverwrite it with a jmp
13:26chadmedyeah but if m1n1's entrypoint is a trampoline that can either start m1n1 or go do that other stuff if coming out of sleep on an already booted system then that becomes """"""easy""""""
13:27chadmedits been on the pile of things to do for years, and at one point there was even a very dirty poc floating around
13:28nickchani mean, wasn't there an issue where the uncore is not powering down on pro/max/ultra on deep wfi
13:29hdbngr has quit [Ping timeout: 480 seconds]
13:29chadmedi have a feeling a lot of our terrible idle power draw is no longer related to the application cores at this point
13:30chadmedbig one i havent a clue how we'd actually investigate is whether or not PSR is actually being used on the laptops for example
13:32nickchanspeaking of trampoline m1n1 entry point kind of has a trampoline now to drop to EL1 from EL3
13:33chaos_princesswe also keep dcp and gpu up.
13:33chaos_princessmacos aggressively turns gpu off when it is not being used
13:34chadmedi played with making pstate 0 the "base" for agx aaages ago and it helped slightly but caused massive performance issues
13:34chaos_princessdoes that turn it off via pmgr?
13:34chaos_princesscause that is what macos does
13:35nickchando we keep dcp on? we have dcp_poweroff() and dcp_poweron() in firmware logs when going to s2idle
13:35chaos_princessit is on via pmgr
13:36chadmednot sure if it goes that far but iirc its supposed to be clock gated at the very least in that state
13:36chaos_princessfor cpus
13:38hdbngr has joined #asahi-dev
13:46hdbngr has quit [Ping timeout: 480 seconds]
13:49jannaudcp is at most clock-gated via "apple,min-state = 4". my understanding for agx was that it has its own aggressive power management
13:50chaos_princessmacos does even further, if you load the pmp tracer, there is constant agx on/off spam
13:56hdbngr has joined #asahi-dev
14:08hardy94 has joined #asahi-dev
14:12kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
14:14hdbngr has quit [Ping timeout: 480 seconds]
14:16kaleryeblueberryoboe has joined #asahi-dev
14:22hdbngr has joined #asahi-dev
14:27kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
14:31hdbngr has quit [Ping timeout: 480 seconds]
14:32hdbngr has joined #asahi-dev
14:38kaleryeblueberryoboe has joined #asahi-dev
14:41hdbngr has quit [Ping timeout: 480 seconds]
14:45hdbngr has joined #asahi-dev
14:59nickchani think when the rvbar entry on primary cpu code path is exercised, the malloc entries will get corrupted
14:59chaos_princessthat is fixable
14:59nickchanafter exercise that code path two times, would result in `dlmalloc: internal error` at least on a7
15:00kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
15:18sventhe first step is to get a PoC running that actually ends up at the entry after a deep sleep wfi. we can then just fix any issues that arive
15:21yukawe need an equivalent of cpu_features->apple_sysregs_unlocked in the proxyclient code, or is there a way to pull cpu features from the running m1n1 to not duplicate them?
15:25svenwe don't guarantee that different versions of proxyclient vs m1n1 work anyway so the only error that could happen is a change to the structure on the m1n1 side without a change to the .py file
15:30yukait should start executing guest code? is the pc part of SPSR which is restored in hv_enter_guest?
15:39kaleryeblueberryoboe has joined #asahi-dev
15:41hdbngr has quit [Ping timeout: 480 seconds]
15:48mattia013 has quit [Remote host closed the connection]
15:49mazjannau: thanks for the feature register dump. I'm glad to see that NV2 is indeed present... could be a replacement for the M2 air one day.
15:50mattia013 has joined #asahi-dev
15:56picnoir has quit [Ping timeout: 480 seconds]
15:57nickchansimply clear cyc_ovrd's wfi_ret and setting wfi force start does not allow boot cpu to restart via wfi at least on t6000
16:00nickchanmicrosoft Windows needs it but clearly you are not the target audience for that kind of stuff
16:04picnoir has joined #asahi-dev
16:23Maya[m]1 has joined #asahi-dev
16:28chaos_princessis pmu related to locked reg or sth else?
16:35hdbngr has joined #asahi-dev
16:42chaos_princessok then
16:44nickchanwith bit [56] set access to ARM PMUv3 registers in EL1 will be trapped to EL2 with EC==0x3f
16:45nickchan has quit [Quit: ZNC 1.9.1+deb2+b3 - https://znc.in]
16:45nickchan has joined #asahi-dev
16:59kaleryeblueberryoboe has quit [Remote host closed the connection]
17:01nickchansven: https://github.com/HoolockLinux/m1n1/blob/1ab9d328d46bca797a2d2cd451cd7553ce6b2a97/proxyclient/experiments/rvbar.py this causes primary cpu to restart, at least on t6000
17:02hdbngr has quit [Ping timeout: 480 seconds]
17:05yukathe question is if you can do this with all cores in a cluster and still have them wake up again somehow
17:06nickchani think it's possible with an IRQ instead of a FIQ but i think i will leave it at this today
17:07nickchansince FIQ is part of the core complxes despite being handled in the "AIC" driver in linux
17:09sveniirc chaos_princess managed to put all cores to sleep but never got them to wake up again :(
17:10chaos_princessi also set a pile of extra stuff in ACC_OVRD, and actually do this on all cores
17:11nickchanthere's a difference if you look at m1n1 code when stopping the cpu there's a deep_sleep switch
17:12chaos_princessdeep sleep = exactly the same as you do in cyc_ovrd, but extra stuff in acc_ovrd
17:12chaos_princessm1n1 also has those
17:12gargantua has joined #asahi-dev
17:16chaos_princessdoesn't work, or i am configuring it wrong
17:16chaos_princessone of the aop gpios is hooked up to lid switch
17:20hardy94 has quit [Quit: hardy94]
17:28hdbngr has joined #asahi-dev
17:33xal_ has quit []
17:34xal has joined #asahi-dev
17:51hdbngr has quit [Ping timeout: 480 seconds]
17:53wabam9391 has joined #asahi-dev
18:00hdbngr has joined #asahi-dev
18:28hardy94 has joined #asahi-dev
18:29mattia013 has quit [Read error: Connection reset by peer]
18:29hardy94 has quit [Remote host closed the connection]
18:35wabam9391 has quit [Ping timeout: 480 seconds]
18:42hdbngr has quit [Ping timeout: 480 seconds]
18:51hdbngr has joined #asahi-dev
19:39gargantua has quit [Ping timeout: 480 seconds]
19:40nora_ has quit [Quit: WeeChat 4.6.3]
19:42pb17 has quit [Ping timeout: 480 seconds]
19:46pb17 has joined #asahi-dev
19:53kaleryeblueberryoboe has joined #asahi-dev
19:54rensenwxre19 has joined #asahi-dev
19:54rensenwxre1 has quit [Read error: Connection reset by peer]
20:35kaleryeblueberryoboe has quit [Read error: Connection timed out]
21:02kaleryeblueberryoboe has joined #asahi-dev
21:10kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
21:10kaleryeblueberryoboe has joined #asahi-dev
21:20kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
21:38Calandracas__ has joined #asahi-dev
21:41hdbngr has quit [Ping timeout: 480 seconds]
21:45Calandracas_ has quit [Ping timeout: 480 seconds]
21:50hdbngr has joined #asahi-dev
21:54Tramtrist has quit [Quit: leaving]
21:54kaleryeblueberryoboe has joined #asahi-dev
21:54Tramtrist has joined #asahi-dev
22:10kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
22:12hdbngr has quit [Ping timeout: 480 seconds]
22:20hdbngr has joined #asahi-dev
22:29hdbngr has quit [Ping timeout: 480 seconds]
22:35kaleryeblueberryoboe has joined #asahi-dev
22:37hdbngr has joined #asahi-dev
22:45chaos_princessCan someone with a t6030 run `python3 proxyclient/tools/run_guest.py --cpus=4 -d -s kernel.development.t6031.14.8.3 dev.kc.macho.development.t6031.14.8.3 -- "debug=0x14e serial=3 -enable-kprintf-spam wdt=-1 pmgr-debug=0xffffffff pmgr-debug-devices=0xffffffff pmgr-debug-always-on=0xffffffff pmgr-debug-energy-model=0xffffffff pmgr-debug-restore-counter=1 pmgr-trace=1 -disable_mtx_chk
22:45chaos_princessclpc=0"` and send me the xnu logs? (substitute your own kernel ofc)
22:47hdbngr has quit [Ping timeout: 480 seconds]
22:56hdbngr has joined #asahi-dev
23:03catred has quit [Remote host closed the connection]
23:03catred has joined #asahi-dev
23:05hdbngr has quit [Ping timeout: 480 seconds]
23:13hdbngr has joined #asahi-dev
23:19kaleryeblueberryoboe has quit [Read error: Connection timed out]
23:22hdbngr has quit [Ping timeout: 480 seconds]
23:25kaleryeblueberryoboe has joined #asahi-dev
23:29hdbngr has joined #asahi-dev
23:33kaleryeblueberryoboe has quit [Ping timeout: 480 seconds]
23:37pb17 has quit [Ping timeout: 480 seconds]
23:41hdbngr has quit [Ping timeout: 480 seconds]
23:42kaleryeblueberryoboe has joined #asahi-dev
23:44pb17 has joined #asahi-dev
23:49hdbngr has joined #asahi-dev
23:54kaleryeblueberryoboe has quit [Remote host closed the connection]
23:54kaleryeblueberryoboe has joined #asahi-dev
23:57hdbngr has quit [Ping timeout: 480 seconds]