#asahi-dev · 2026-10-28 09:53
jannauindeed. I did not run into issues since I enabled just dcp in m1n1#asahi-dev · 2026-10-28 09:51
jannauthe dcpext nodes can be added, diabled and without aliases. I think #608 has at least some dcpext nodes#asahi-dev · 2026-10-28 09:49
jannauyes. that my plan. I applied #608 locally for 7.3 and have some small fixes/changes#asahi-dev · 2026-10-28 09:47
jannaut8122 however will only have dcpext but doesn't conflict with t603x-j514*#asahi-dev · 2026-10-28 09:45
jannauyuka: just rename things to them more consistent. but t6030 should have dcpext0 / dcpext1#asahi-dev · 2026-10-28 09:34
jannaua comment explaining differences to all other devices is helpful#asahi-dev · 2026-10-28 09:33
jannaulet's try to replicate what's in the ADT and deviate from it only if that does not work#asahi-dev · 2026-10-28 09:31
jannauyes, aliases just for the used dcpext#asahi-dev · 2026-10-28 09:18
jannauhttps://github.com/sofus13/libva-v4l2_request/commit/53bbc5662bd1deff0d92c1001023bc91a64beb32 suggest we don't plan to upstream#asahi-dev · 2026-10-28 09:16
jannauyuka: for usable dcpext your diff is missing to add dispext* to 'display's "iommus"#asahi-dev · 2026-10-28 09:15
jannauyuka: I think the darts are not disabled. the dcpext are enabled via aliases#asahi-dev · 2026-10-28 09:12
jannauwe could of course just install an asahi_drv_video.so symlink#asahi-dev · 2026-10-28 09:11
jannauinspired by https://github.com/radxa-pkg/qcom-va-driver which is libva_v4l2 under different name#asahi-dev · 2026-10-28 09:11
jannausofus: maybe we should rename libva_v4l2_request to asahi-va-driver? that way we can install it as asahi_drv_video.so and libva will use it automatically (based on the DRM driver name). we also do not clash with the existing libva_v4l2_request package (on fedora for example)#asahi-dev · 2026-10-28 08:38
jannauthis is from testing on hw, wifi did not work but I haven't looked at it at all#asahi-dev · 2026-10-28 08:33
jannauMichaelReeves[m]: no problem. I need to look more closely at your series. it might break bcm4387 (M1 Pro / Max devices)#asahi-dev · 2026-10-28 08:21
jannauyuka: "apple-dcp 2cac00000.dcp: error 0000000000000000: Failed to created PIODMA iommu child device" either try again or there's something wron in the dt#asahi-dev · 2026-10-28 08:19
jannauunfortunately hard to reproduce#asahi-dev · 2026-10-28 08:19
jannauI see occasional null pointer derefs under the HV because the piodma subdevice fails to initialize#asahi-dev · 2026-10-28 08:14
jannauack. that's the minimal change that makes it work here as well#asahi-dev · 2026-10-28 08:12
jannauno, we turning something off too much. pd_ignore_unused is not required#asahi-dev · 2026-10-28 08:10
jannauon t6031#asahi-dev · 2026-10-28 08:10
jannauyuka: dcp works in linux with pd_ignore_unused and "apple,min-state = <4>;" sprinkled over more disp power-states#asahi-dev · 2026-10-28 08:06
jannauI might have been misguided by crashlog buffer though#asahi-dev · 2026-10-28 08:06
jannauthe iova allocator from dart.py. the default overlaps with already allocated iova#asahi-dev · 2026-10-27 21:54
jannauI think the most important "fixes" are `iova_range` for dart-dcp and `stream=5` for the DCPClient#asahi-dev · 2026-10-27 21:53
jannauyuka: current diff: https://gist.github.com/jannau/674850a3d03d7e10bceefd1e13f5c5a1#asahi-dev · 2026-10-27 21:43
jannauyes, m3 / m3 pro work#asahi-dev · 2026-10-27 21:31
jannauwhich would explains why nothing happens after that#asahi-dev · 2026-10-27 21:31
jannau0x__0 is type DCPEp_SetShmem, 0x_4_ is flag which was sent. 0x1__ is unknown. since we haven't seen DCPEp_SetShmem messages from DCP I guess it's an error#asahi-dev · 2026-10-27 21:28
jannauthe firmware answers the SetShmem init call with 0x140 which to my best guess is an error return#asahi-dev · 2026-10-27 21:26
jannauI've fixed experiments/dcp.py enough to work to get to the same point as the linux driver.#asahi-dev · 2026-10-27 20:23
jannauyes, booted to login screen#asahi-dev · 2026-10-27 20:23
jannauthat seems to do the trick#asahi-dev · 2026-10-27 19:34
jannauyuka: does t6034 boot macos somewhat relieable under the hypervisor? Any special boot flags or patches? t6031 panics somewhat reliably due to 2-3 timeouts#asahi-dev · 2026-10-27 18:23
jannauwhy apple? j514c ADT has in aliases "dcp0 = /arm-io/dcp0" but the dcp node is "dcp"#asahi-dev · 2026-10-27 17:47
jannaudcp on j514s / t6030 works as well#asahi-dev · 2026-10-27 17:47
jannautoggling random smc GPIOs might break things#asahi-dev · 2026-10-27 17:29
jannaudcp on t8122 is working, not sure if I ned to add compatible or DCP FW versions checks to dcpep_cb_map_reg(). t8122 / 14.7.0 doesn't need the registers mapped but expects the mmio address as dva back#asahi-dev · 2026-10-27 16:56
jannaum3 max#asahi-dev · 2026-10-27 16:56
jannauerr, j514m/c#asahi-dev · 2026-10-27 16:55
jannauis j514s' dart locked, does it have four levels set?#asahi-dev · 2026-10-27 15:07
jannauI bumped the heap to 428MB. I guess I'll add a command line parameter so that run_guest_kernel.sh can request a size for my huge boot images#asahi-dev · 2026-10-27 15:04
jannauyep, that was it#asahi-dev · 2026-10-27 15:03
jannaumaybe my fault, increased the heap in run_guest.py quite a bit to load initramfs with modules and debug symbols#asahi-dev · 2026-10-27 15:00
jannauyes. I assume it's the ADT property "/chosen/dram-base" but that's 0x10000000000ULL in the HV's ADT. same for hv.ram_base#asahi-dev · 2026-10-27 14:46
jannauyes#asahi-dev · 2026-10-27 14:42
jannauI have changes in hv/__init__.py so I might screwed up in rebasing#asahi-dev · 2026-10-27 14:42
jannausven: can you think of anything which could cause: "t8110dart.c:1283 Assertion failed: dram_base == 0x800000000ULL || dram_base == 0x10000000000ULL". macos 14.8.3 on t8122/m3#asahi-dev · 2026-10-27 14:02
jannauerr, no. pmgr_dcp and the offsets are probably just wrong