#
…

2026-05-28

00:05truita_ has joined #asahi-dev
00:07truita has quit [Ping timeout: 480 seconds]
00:09truita_ is now known as truita
00:10gargantua has quit [Ping timeout: 480 seconds]
00:11gargantua has joined #asahi-dev
00:35liangqi has joined #asahi-dev
00:43liangqi has quit [Ping timeout: 480 seconds]
00:45damas has quit [Read error: Connection timed out]
01:07marvin24 has joined #asahi-dev
01:35jsk_ has joined #asahi-dev
01:40jsk has quit [Ping timeout: 480 seconds]
01:43jsk_ is now known as jsk
01:44Calandracas__ has joined #asahi-dev
01:49ipatch_ has quit [Quit: WeeChat 4.9.0]
01:50ipatch has joined #asahi-dev
01:51Calandracas_ has quit [Ping timeout: 480 seconds]
02:20liangqi has joined #asahi-dev
02:24tobhe has joined #asahi-dev
02:29liangqi has quit [Ping timeout: 480 seconds]
02:31tobhe_ has quit [Ping timeout: 480 seconds]
02:47voidah has quit [Ping timeout: 480 seconds]
02:49voidah has joined #asahi-dev
02:53caszue has quit [Read error: Connection reset by peer]
02:53caszue has joined #asahi-dev
02:59voidah has quit [Ping timeout: 480 seconds]
03:02damas has joined #asahi-dev
03:07voidah has joined #asahi-dev
03:14Lyude has quit [Quit: Bouncer restarting]
03:16Lyude has joined #asahi-dev
03:21pb17 has quit [Ping timeout: 480 seconds]
03:22pb17 has joined #asahi-dev
03:24voidah has quit [Ping timeout: 480 seconds]
03:32voidah has joined #asahi-dev
03:35damas has quit [Remote host closed the connection]
03:36damas has joined #asahi-dev
03:40voidah has quit [Ping timeout: 480 seconds]
03:46lion328 has quit [Ping timeout: 480 seconds]
03:49voidah has joined #asahi-dev
03:54liangqi has joined #asahi-dev
03:56lion328 has joined #asahi-dev
03:56nora_ has joined #asahi-dev
03:57voidah has quit [Ping timeout: 480 seconds]
03:58nora has quit [Ping timeout: 480 seconds]
04:00damas has quit [Remote host closed the connection]
04:01damas has joined #asahi-dev
04:03liangqi has quit [Ping timeout: 480 seconds]
04:07voidah has joined #asahi-dev
04:08gargantua has quit [Ping timeout: 480 seconds]
04:13kaguya_ has quit [Quit: Connection closed for inactivity]
04:22liangqi has joined #asahi-dev
04:23voidah has quit [Ping timeout: 480 seconds]
04:26udkh[m] has joined #asahi-dev
04:30voidah has joined #asahi-dev
04:30liangqi has quit [Ping timeout: 480 seconds]
04:38liangqi has joined #asahi-dev
04:38voidah has quit [Ping timeout: 480 seconds]
04:44pb17 has quit [Ping timeout: 480 seconds]
04:47pb17 has joined #asahi-dev
04:47voidah has joined #asahi-dev
04:56voidah has quit [Ping timeout: 480 seconds]
04:56liangqi has quit [Ping timeout: 480 seconds]
05:05voidah has joined #asahi-dev
05:08damas has quit [Ping timeout: 480 seconds]
05:13voidah has quit [Ping timeout: 480 seconds]
05:16voidah has joined #asahi-dev
05:19liangqi has joined #asahi-dev
05:24voidah has quit [Ping timeout: 480 seconds]
05:31liangqi has quit [Ping timeout: 480 seconds]
05:33voidah has joined #asahi-dev
05:35Aidan[m] has joined #asahi-dev
05:40liangqi has joined #asahi-dev
05:42voidah has quit [Ping timeout: 480 seconds]
05:49liangqi has quit [Ping timeout: 480 seconds]
05:49voidah has joined #asahi-dev
05:56liangqi has joined #asahi-dev
05:58voidah has quit [Ping timeout: 480 seconds]
05:58nnym has quit [Read error: No route to host]
05:58nnym has joined #asahi-dev
06:04liangqi has quit [Ping timeout: 480 seconds]
06:05voidah has joined #asahi-dev
06:25voidah has quit [Ping timeout: 480 seconds]
06:35voidah has joined #asahi-dev
06:39sofus has joined #asahi-dev
06:44liangqi has joined #asahi-dev
06:45bennofs1 has joined #asahi-dev
06:46bennofs has quit [Read error: Connection reset by peer]
06:46bennofs1 is now known as bennofs
06:50voidah has quit [Ping timeout: 480 seconds]
06:59voidah has joined #asahi-dev
07:08voidah has quit [Ping timeout: 480 seconds]
07:11snooze6214[m]Hey, has anyone gotten m1n1 to run in proxy mode on the macbook neo? Mine says that it's running in proxy mode but it does not appear as a serial device when connecting to my linux host using a usb C to usb A cable.
07:14StanfordAppliedCyber[m]it's a pain, and you need another apple silcion mac and a very nice usb cable
07:15snooze6214[m]need another apple silicon mac? did you use macvdmtool? Stanford Applied Cyber
07:16StanfordAppliedCyber[m]..........I don't want to be mean but please RTFM
07:16StanfordAppliedCyber[m]specifically the macvdmtool readme
07:16snooze6214[m]ykw valid lol, thanks
07:17damas has joined #asahi-dev
07:17voidah has joined #asahi-dev
07:18StanfordAppliedCyber[m]also i'm doing a bunch of dev work on the macbook neo right now, tl;dr i'm trying to port the m1n1 hypervisor to the macbook neo by emulating SPTM. my emulator is tainted and thus can't be upstreamed (with the exception of the UAT endpoints which are completely clean) but i'm committed to writing very nice clean room docs and finding a way to get it upstreamed so that others can start REing the neo
07:19StanfordAppliedCyber[m]i'm almost to userspace
07:22StanfordAppliedCyber[m]not to mention every other SPTM enabled device
07:25damas has quit [Ping timeout: 480 seconds]
07:26voidah has quit [Ping timeout: 480 seconds]
07:34voidah has joined #asahi-dev
07:43sofusI decided to try v4l2 for avd. It scores 57/135 on the JVT-AVC_V1 test suite, which i think is okay compared to the 76/135 macos gets
07:43voidah has quit [Ping timeout: 480 seconds]
07:46xal has quit [Read error: Connection reset by peer]
07:47xal has joined #asahi-dev
07:48JamesCalligeros[m]Do you have an avd v4l2 driver?
07:48sofusIm writing one
07:51voidah has joined #asahi-dev
07:52jannausnooze6214[m]: usb device mode doesn't work on the neo since there's a usb2 hub (there ought a way to bypass the hub but we don't know how)
07:59sofusIs v4l2 okay? Im not sure how much support it has, firefox does not seem to support it...
07:59voidah has quit [Ping timeout: 480 seconds]
08:00JamesCalligeros[m]Well it’s either v4l2 or vulkan video. Search the logs for previous discussions on this
08:02asahi has joined #asahi-dev
08:05sofusI have searched, it just seemed like v4l2 was not prefered
08:09voidah has joined #asahi-dev
08:17voidah has quit [Ping timeout: 480 seconds]
08:18asahi has quit [Quit: asahi]
08:18voidah has joined #asahi-dev
08:24asahi has joined #asahi-dev
08:27voidah has quit [Ping timeout: 480 seconds]
08:28jannauI'd continue for now, a working driver is better than none. From the working driver either support can be added (there are other platforms with v4l2 drivers) or it can be used as base to rewrite the driver
08:34sofusOkay, thanks
08:35voidah has joined #asahi-dev
08:36chaos_princessseconding "some driver is better than none", but an advantage of vkvideo/vaapi is that a significant chunk of your driver can live in userspace instead of in the kernel.
08:38mazjannau: does CS work on neo? if it doesn't, I'd better capture that in the doc.
08:42snooze6214[m]jannau: ah I see, thanks
08:44voidah has quit [Ping timeout: 480 seconds]
08:47sofuschaos_princess: i get that. My hope is that the driver esentially copies v4l2's structs to the cm3
08:47sofuswhich seems possible (at least for h264)
08:47chaos_princesswasn't the plan to ignore the cm3?
08:48JamesCalligeros[m]eiln was going to ignore the m3 interface and talk directly to the actual decoder blocks wasnt she?
08:48sofusKinda, we kinda need it for irq
08:49chaos_princesscan't you reconfigure the aic to get the interrupts to ap cores?
08:49sofusbut yes, everything i have done is based on her work
08:49chaos_princessor if you can't - just proxy the irq and that's it
08:49sofuschaos_princess: im not sure
08:49sofuschaos_princess: thats what im doing right now
08:50jannaumaz: uart over SBU works. over DATA should work as well since the port controller does the muxing
08:52mazjannau: ah, cool. thanks for letting me know.
08:53sofusim talking about writing our own firmware for the cm3 if it was not clear
08:53mazFWIW, I have a patch to allow enabling debugusb from the CS interface. gives you two uarts, just in case! ;-)
08:53voidah has joined #asahi-dev
08:55chaos_princesssofus: yea, that's kinda what i meant by "just proxy the irq", but are you trying to put a bunch of logic into the new cm3 firmware that parses the v4l structs and feeds the hw?
09:00sofuschaos_princess: no, but i think at some point (when everything works), offloading work to the cm3 is a good idea. And i dont think the instruction stream generation belongs in the kernel
09:01voidah has quit [Ping timeout: 480 seconds]
09:01chaos_princessright, so, from my understanding v4l2 has all the parts in kernel, with no userspace part that can generate the instruction stream
09:02asahi has quit [Quit: asahi]
09:03JamesCalligeros[m]If you want to delegate responsibilities to userspace youd be better off skipping v4l2 and implementing a drm/accel device and using vk video
09:03JamesCalligeros[m]Getting the m3 to do stuff isnt a bad idea either but i would be wary of NIHing a firmware interface if it’s not necessRy
09:04chaos_princessdrm/accel is actually kind of a perfect fit for this kind of thing - you have map/unmap memory, and "run a command buffer" api. Should be all you'd want
09:04sofusI would rather do it on the cm3, but i need to look more into the other codecs before i know if its possible
09:05chaos_princesswhy not use the (hopefully much faster) ap cores to generate the command stream?
09:05chaos_princessnot like the command stream is big, but still
09:07sofusI will need to look into a few more things before i have a real answer
09:07leiosofus: I've been told that if you look at eiln's stuff and compare against driver/media/platform/verisilicon or drivers/media/platform/rockchip decoder drivers, you'll find some strangely similar parameters and patterns, same kind of address and offsets, so you might find some inspiration from there. TI released some open source codec drivers for now abandonned Imagination CODEC; these where hybrid, you could do firmware access, or cpu access; Imagination gave on
09:07leio on these chip concurrently to Apple giving up on them, don't think it was a coincidence, and since we know by now that the GPU is somewhat of a fork of Imagination design, its a possiblilty that the codecs are a fork of their design too; at least for the old codec, and how to compute auxiliary / scratch buffer sizes, that might be key
09:08leiothese were*; gave up*
09:09leio(I guess old codec meant like H.264 in that?)
09:09sofusleio: ha that actually makes sense! I have used verisilicon as reference (and copied a lot), i will look into rockchip also, thanks!
09:11voidah has joined #asahi-dev
09:28voidah has quit [Ping timeout: 480 seconds]
09:38voidah has joined #asahi-dev
09:39asahi has joined #asahi-dev
09:46voidah has quit [Ping timeout: 480 seconds]
09:49hightower2 has joined #asahi-dev
09:54voidah has joined #asahi-dev
09:54xal has quit []
09:56xal has joined #asahi-dev
10:08voidah has quit [Ping timeout: 480 seconds]
10:11minecrell has quit [Ping timeout: 480 seconds]
10:16voidah has joined #asahi-dev
10:17minecrell has joined #asahi-dev
10:29voidah has quit [Ping timeout: 480 seconds]
10:29asahi has quit [Ping timeout: 480 seconds]
10:31minecrell has quit [Quit: Ping timeout (120 seconds)]
10:33minecrell has joined #asahi-dev
10:37voidah has joined #asahi-dev
10:45voidah has quit [Ping timeout: 480 seconds]
10:50yukaRe macbook neo usb device mode
10:50yukaa friend noted that the usb-repeater is likely responsible for bypassing the usb-hub
10:51yukaWe know the usb-hub is a variant of the Via VL122 (https://www.via-labs.com/product_show.php?id=126). While it is not super obvious, it seems unlikely to me now that the upstream/downstream ports of this hub can be reversed.
10:52yukaThe device tree says the usb-repeater is a "ticd2e22", ti = texas instruments, cd = custom design?, it's probably related to this one: https://www.ti.com/lit/ds/symlink/tusb2e221.pdf
10:53yukabut not the same, since the i2c register map seems to be completely different
10:53yukabut all variants of ti 2e22 usb repeaters I can find do have a 2x2 crosspoint mux
10:54yukaOn TIUSB2E221 (which is a newer variant of TIUSB2E22 with i2c) the 2x2 crosspoint mux is controlled via a gpio
10:55yukathe device tree doesn't mention anything of a gpio
10:55voidah has joined #asahi-dev
10:55yukait is possible that apple's custom variant allows controlling it over i2c
10:56yukaFor some reason I can't properly dump the i2c regs using the m1n1 code. Maybe because it doesn't implement the correct i2c reading mode (I know too little about i2c...)
10:56yukaBut if I managed to enter device mode in Mac OS, I would now try to focus the regs of the _repeater_ (I2C addr 0x21), and not the hub.
11:00hightower3 has joined #asahi-dev
11:03voidah has quit [Ping timeout: 480 seconds]
11:05Yushi has quit [Remote host closed the connection]
11:06Yushi has joined #asahi-dev
11:07hightower2 has quit [Ping timeout: 480 seconds]
11:12voidah has joined #asahi-dev
11:26asahi has joined #asahi-dev
11:29voidah has quit [Read error: Connection timed out]
11:37voidah has joined #asahi-dev
11:46voidah has quit [Ping timeout: 480 seconds]
11:49asahi1 has joined #asahi-dev
11:50voidah has joined #asahi-dev
11:53asahi has quit [Ping timeout: 480 seconds]
11:53asahi1 is now known as asahi
12:14yukaHow do you all record/save your hv traces?
12:14yukasince I have to interact with the shell to start it properly, and also piping the output somewhere doesn't seem to work
12:15yukaand my scrollback buffer is too small to copy it afterwards
12:15chaos_princessi just set infinite scrollback
12:16yukaAh well
12:16chaos_princessboth Konsole and stock macos terminal support that
12:17yukaI use foot
12:18yukaI guess I'll need to switch over to something more fancy for this
12:18yukabut having traces go to another iodev would be nice
12:19asahi has quit [Quit: asahi]
12:23jannauthere's `-l` to log to files, note that not everything uses log. there are things only printed to the terminal
12:24yukanice, thanks
12:28fl0_d has joined #asahi-dev
12:30yukaAh, this also works: 2>&1 | tee -i /path/to/log
12:30yukajust the shell is slightly broken then
12:31yukabut good enough
12:33liangqi has quit [Remote host closed the connection]
12:35xal has quit [Read error: Connection reset by peer]
12:36xal has joined #asahi-dev
12:42liangqi has joined #asahi-dev
12:44voidah has quit [Ping timeout: 480 seconds]
12:46damas has joined #asahi-dev
12:53voidah has joined #asahi-dev
12:53donaldh has quit [Remote host closed the connection]
12:55damas has quit [Ping timeout: 480 seconds]
12:57liangqi has quit [Remote host closed the connection]
12:58liangqi has joined #asahi-dev
12:58fl0_d has quit [Ping timeout: 480 seconds]
13:01damas has joined #asahi-dev
13:01voidah has quit [Ping timeout: 480 seconds]
13:02tobhe has quit [Ping timeout: 480 seconds]
13:05tobhe has joined #asahi-dev
13:11voidah has joined #asahi-dev
13:14liangqi has quit [Ping timeout: 480 seconds]
13:18damas has quit [Read error: Connection timed out]
13:19voidah has quit [Ping timeout: 480 seconds]
13:24liangqi has joined #asahi-dev
13:27voidah has joined #asahi-dev
13:28gargantua has joined #asahi-dev
13:31tobhe has quit [Remote host closed the connection]
13:35tobhe has joined #asahi-dev
13:36voidah has quit [Ping timeout: 480 seconds]
13:42sofus has quit [Ping timeout: 480 seconds]
13:43voidah has joined #asahi-dev
13:52voidah has quit [Ping timeout: 480 seconds]
13:57RZ302 has joined #asahi-dev
13:59voidah has joined #asahi-dev
14:05gargantu1 has joined #asahi-dev
14:05gargantua has quit [Ping timeout: 480 seconds]
14:08voidah has quit [Ping timeout: 480 seconds]
14:18voidah has joined #asahi-dev
14:26voidah has quit [Ping timeout: 480 seconds]
14:35voidah has joined #asahi-dev
14:36liangqi has quit [Ping timeout: 480 seconds]
14:37RZ302 has quit [Remote host closed the connection]
14:38fl0_d has joined #asahi-dev
14:42RZ302 has joined #asahi-dev
14:42sklugHey everyone. I am at Embedded Recipes in Nice and wanted to do a presentation using a M2 MBP with HDMI out. Unfortunately the HDMI detection failed and we ony got garbage on the output. After reboot it kind of worked, but I still saw rendering issues. Is there any debug data I could collect that might help in debugging the issue afterwards?
14:43voidah has quit [Ping timeout: 480 seconds]
14:45liangqi has joined #asahi-dev
14:48chaos_princessobligatory check with macos, attach dmesg, probably grab the edid of the device you were trying to use.
14:53fl0_d has quit [Ping timeout: 480 seconds]
14:53voidah has joined #asahi-dev
14:55yukaI traced pcie on M3 Max (the 14 core one, T6034 if it matters), but I saw none of the fuses stuff
14:57yukaas in mac os booted in the hv after a bit of fiddling and a few more tries
14:57gargantua has joined #asahi-dev
14:58chaos_princessso, i strongly suspect fuses are only applied on sleep exit as, iboot already does it for us on cold boot
14:59chaos_princesswell, not fuses, the other new calibrations
14:59chaos_princessfuses no longer seem to be a thing past t602x
15:00gargantu1 has quit [Ping timeout: 480 seconds]
15:00yukaregs apcie[5-7] are not accessed at all
15:01chaos_princessdid you manage to get macos to fully boot? i wasn't able to, it kept crashing
15:01chaos_princessso i only got the early parts of init, and yolo-d the rest.
15:02yukaI added --cpus 4
15:03yukaOh, cool
15:03chaos_princessnot the latest of what i have, 692 should use the same as t8122, m1n1 init succeeds, but linux complains that it can't get link up
15:03voidah has quit [Ping timeout: 480 seconds]
15:04chaos_princessalso remove erroring out on failing to init pmgr, there are some weird pmgrs that remain stuck in state 3 instead of going to f
15:04sklugchaos_princess: A paste of dmesg grepped for dcp: https://paste.debian.net/hidden/92869b8b That was a partly sucessful run. The dmesg of the failed run is unfortunately lost.
15:05chaos_princessoh, and you want to add multi-pmgr support to dart and pcie drivers, just use the helper and it works.
15:05chaos_princessthere are now like 4 "root" pmgrs for some reason that it wants up
15:05chaos_princessor set it to pd_ignore_unused
15:06jannauchaos_princess: failing pmgr init in m1n1? I did https://github.com/AsahiLinux/u-boot/commit/3b233f59d0b6b57eae5add46a6fa7787ea11388e in u-boot for apcie_st/gp power states
15:06jannauthe linux driver clears APPLE_PMGR_AUTO_ENABLE
15:07chaos_princessyea, those weird things
15:07chaos_princessapcie_sys_st is one of them
15:08chaos_princessbasically every apcie_sys_* is like that
15:08RZ302 has quit [Remote host closed the connection]
15:09jannaufor the linux devicetree I intend to use t6031 for {t6031, t6032, t6034}
15:10jannauyuka: do you have MIDR part numbers for t6034? I suspect those are the same as t6031/t6032
15:12jannauyes, I decided to ignore them to preserve the on-boot state but after clearing the AUTO_ENABLE bit they turn on as expected
15:12voidah has joined #asahi-dev
15:13chaos_princessin case of m1n1 pcie init - it calls pmgr_adt_enable, and that errors out on them as it wants them to reach state f, which they aren't doing. i just commented out the error return in my local branch
15:14jannausklug: do you have journald? `journalctl -k -o short-monotonic --no-hostname -b-${N} -g dcp` probably will recover the failed log with the correct value of N. drop the "-o short-monotonic" to find the right boot by timestamp
15:16yukajannau: indeed, my boot core says CPU part: 0x49 M3 Max Everest
15:16yukaI strongly suspect the E-Core part number is also the same as on T6031
15:17yukadon't know from the top of my head how to get it in m1n1
15:20alessaba has quit [Ping timeout: 480 seconds]
15:20alessaba has joined #asahi-dev
15:20voidah has quit [Ping timeout: 480 seconds]
15:20yuka0x48 is the other one
15:23yuka(used your switch_boot_cpu branch to get it)
15:24RZ302 has joined #asahi-dev
15:29voidah has joined #asahi-dev
15:33RZ302 has quit [Ping timeout: 480 seconds]
15:33liangqi has quit [Ping timeout: 480 seconds]
15:37pb17 has quit [Ping timeout: 480 seconds]
15:42liangqi has joined #asahi-dev
15:44voidah has quit [Ping timeout: 480 seconds]
15:44pb17 has joined #asahi-dev
15:46sklugjannau: Thanks for the hint. I did wrong on the -b parameter. Here is the paste: https://paste.debian.net/hidden/ec36f1ca
15:52voidah has joined #asahi-dev
15:56RZ302 has joined #asahi-dev
16:01voidah has quit [Ping timeout: 480 seconds]
16:04gargantua has quit [Ping timeout: 480 seconds]
16:04RZ302 has quit [Ping timeout: 480 seconds]
16:06liangqi has quit [Ping timeout: 480 seconds]
16:08voidah has joined #asahi-dev
16:15liangqi has joined #asahi-dev
16:17voidah has quit [Ping timeout: 480 seconds]
16:20gargantua has joined #asahi-dev
16:23hightower3 has quit []
16:24liangqi has quit [Ping timeout: 480 seconds]
16:24voidah has joined #asahi-dev
16:25liangqi has joined #asahi-dev
16:28RZ302 has joined #asahi-dev
16:33voidah has quit [Ping timeout: 480 seconds]
16:33alexanderden[m] has joined #asahi-dev
16:37voidah has joined #asahi-dev
16:38liangqi has quit [Ping timeout: 480 seconds]
16:45RZ302 has quit [Ping timeout: 480 seconds]
16:56liangqi has joined #asahi-dev
17:08liangqi has quit [Ping timeout: 480 seconds]
17:16gargantu1 has joined #asahi-dev
17:16gargantua has quit [Ping timeout: 480 seconds]
17:16liangqi has joined #asahi-dev
17:17yukaRe pmgr, mac os reads APCIE_SYS_GP as 0x1000030f, writes it back as 0x1000000f
17:18yukalater, it reads it back again and it has value 0x1f0003ff
17:18yukaSo I'm not sure PMGR_AUTO_ENABLE is involved?
17:19yukamore like it clears PMGR_WAS_CLKGATED and PMGR_WAS_PWRGATED
17:28liangqi has quit [Ping timeout: 480 seconds]
17:42liangqi has joined #asahi-dev
17:51yukaOn t6031 pcie, the polling of state->phy_base[0] + 0x8 happens _before_ APCIE_PHYCMN_CLK is set (unless the order got messed up in tracing?)
17:51liangqi has quit [Ping timeout: 480 seconds]
17:55chaos_princessthere are situations where you can reorder stuff and it still works
17:56yukasure, but the code implies causality here
17:57yuka"pcie: PHY clock enable timed out"
18:20fl0_d has joined #asahi-dev
18:58RZ302 has joined #asahi-dev
19:00cy8aer has quit [Remote host closed the connection]
19:07RZ302 has quit [Ping timeout: 480 seconds]
19:12RZ302 has joined #asahi-dev
19:13liangqi has joined #asahi-dev
19:15lukeleppan91 has quit [Ping timeout: 480 seconds]
19:21cy8aer has joined #asahi-dev
19:21RZ302 has quit [Ping timeout: 480 seconds]
19:24lukeleppan91 has joined #asahi-dev
19:26fl0_d has quit [Ping timeout: 480 seconds]
19:30liangqi has quit [Ping timeout: 480 seconds]
19:37liangqi has joined #asahi-dev
19:45liangqi has quit [Ping timeout: 480 seconds]
19:47RZ302 has joined #asahi-dev
19:47liangqi has joined #asahi-dev
19:51yurix has joined #asahi-dev
19:55RZ302 has quit [Ping timeout: 480 seconds]
19:58fl0_d has joined #asahi-dev
19:59liangqi has quit [Ping timeout: 480 seconds]
19:59yurix has quit [Remote host closed the connection]
20:00yurix has joined #asahi-dev
20:11RZ302 has joined #asahi-dev
20:12RZ302 has quit [Remote host closed the connection]
20:12gargantua has joined #asahi-dev
20:13gargantu1 has quit [Ping timeout: 480 seconds]
20:15liangqi has joined #asahi-dev
20:19liangqi has quit [Remote host closed the connection]
20:19liangqi has joined #asahi-dev
20:28RZ302 has joined #asahi-dev
20:33yukaI see a wifi device in linux lspci :-)
20:33yukaOn T6040
20:34yukavery unsure how to structure the pcie nodes in the linux dt
20:34chaos_princessshould be the same as t602x?
20:35chaos_princesswhat was the missing parts?
20:36yukaThe regs of apcie{,0} seem to be similar / the same for all of t603{0,1,2,4}. t6030 has an apcie,t6030 compatible and one less per-port reg (which we don't use, but having it means we interpret the last reg as intr2axi in m1n1)
20:36RZ302 has quit [Ping timeout: 480 seconds]
20:37yukaj575d has apcie0@580000000 and apcie1@2580000000
20:37yukaI assume this means it has an apcie on both dies?
20:37yukabut then it only has the dart-apcie* on die0
20:38yukaI don't know how to wire this up properly with the multi die stuff
20:38fl0_dyuka, which one is j575d?
20:39yukaM3 Ultra Mac Studio
20:39yukaAlso is the apcie1 on j575d used for anything? it doesn't have any bridges
20:39chaos_princessdon't bother with ultra for now, i think this one is sptm-ed
20:39StanfordAppliedCyber[m]oh btw yuka if traces would help lmk, more than happy to assist
20:40chaos_princessi think the other half of the ssd hangs off apcie1 on ultras
20:40fl0_dah. I think comparing t602x stuff with the multi-die parts that jannau already did in bits/001-devicetree-m3 should help with layouting DT
20:41yukaBelieve me, I stared at that for the last two hours
20:41chaos_princessfeel free to send what you have working on pro/max, we will clean it up for ultra
20:41fl0_dyuka, sorry...
20:42yukaOk. If we ignore the apcie1 on the M3 Ultra, I would put the pcie nodes in t6031-die0.dtsi
20:42jannauignore apcie1 / ultra. I don't think we need it and it should be used for ssd nand
20:43jannauack on die0
20:44ddxtanx has quit [Remote host closed the connection]
20:51yukaI have no idea how similar apcie,t6030 and apcie,t6031 are. For now I called the new variant T603X, but if I could get my hands on t6030 pcie traces I would double check if this needs to be handled separately.
20:52chaos_princessmacos outright has separate kexts for them, so i'd expect some differences
20:54jannauplease use t6031 for max/ultra. I would be surprised if we have to make distinctions between t6031 and t6034 (possibly with a few exceptions in m1n1)
20:57yukaOk, changed the variant's name to T6031.
21:00yukaIt might be more appropriate to do the clearing PMGR_WAS_{CLK,PWR}GATED in "Cleaning up device states"
21:00yukaI'm not yet sure
21:01jannauI'd do it in the mask32() which sets the target mode like linux does
21:03yukaSo Linux unconditionally clears these flags on each ps_set...?
21:04yukabtw the devices still don't reach their enabled state immediately after, and mac os also doesn't poll for them
21:04yukait's very weird
21:06fl0_d has quit [Ping timeout: 480 seconds]
21:07jannauthey probably turn on if you clear APPLE_PMGR_AUTO_ENABLE as well
21:07yukayep, tried that
21:16tobhe_ has joined #asahi-dev
21:18fl0_d has joined #asahi-dev
21:23tobhe has quit [Ping timeout: 480 seconds]
21:24tobhe_ has quit [Ping timeout: 480 seconds]
21:26tobhe has joined #asahi-dev
21:29gargantua has quit [Ping timeout: 480 seconds]
21:33chaos_princesslol, this is almost exactly my local branch except for pmgr which i screwed up
21:36fl0_d has quit [Ping timeout: 480 seconds]
21:39RZ302 has joined #asahi-dev
21:45druz has joined #asahi-dev
21:47liangqi has quit [Remote host closed the connection]
21:47liangqi has joined #asahi-dev
21:48RZ302 has quit [Ping timeout: 480 seconds]
21:56liangqi has quit [Ping timeout: 480 seconds]
21:59liangqi has joined #asahi-dev
22:09liangqi has quit [Ping timeout: 480 seconds]
22:11gargantua has joined #asahi-dev
22:18fl0_d has joined #asahi-dev
22:31fl0_d has quit [Ping timeout: 480 seconds]
22:32liangqi has joined #asahi-dev
22:40druzsofus / others: I had been planning to do an h.264 AVD driver for my UiO master thesis with drm/accel and VA-API, didn't realize anyone was working it. Don't want to duplicate or step over any work. Is this still worth doing?
22:43liangqi has quit [Ping timeout: 480 seconds]
22:58liangqi has joined #asahi-dev
23:07liangqi has quit [Ping timeout: 480 seconds]
23:08liangqi has joined #asahi-dev
23:33chadmed has quit [Quit: Konversation terminated!]
23:34liangqi has quit [Remote host closed the connection]
23:37fl0_d has joined #asahi-dev
23:38liangqi has joined #asahi-dev
…