#asahi-dev · 2023-04-25 07:36
jannauif you move it, it has a t6020-pmgr-misc in .compatible#asahi-dev · 2023-04-25 07:23
jannauSErrors but the HV complains first https://gist.github.com/jannau/526d76696ab10f0ac2308151fc68d975 #asahi-dev · 2023-04-25 07:18
jannauno problems with dcp though#asahi-dev · 2023-04-25 07:18
jannauI see dart translation faults for 583008000.iommu on s2idle and the nvme didn't boot on the second resume#asahi-dev · 2023-04-25 07:11
jannaudoes pmgr-misc exist on die 1? I'm getting transalation faults on 0x228e20c000 and 0x228e20c800 on m1 ultra#asahi-dev · 2023-04-24 19:24
jannauI'd expect that 640x480 is the minimal resolution this was tested against#asahi-dev · 2023-04-24 19:23
jannauI suspect the problem is that simply doesn't expect that v sync, front/back porch can can be that large compred to the vertical resolution#asahi-dev · 2023-04-24 19:20
jannauno, it should be equivalent to the CVT-RB values but don't ask me why it isn't#asahi-dev · 2023-04-24 19:16
jannausimply fill the mode manually with the values that timing generator reports for CVT-RBv2#asahi-dev · 2023-04-24 19:15
jannauI'd simply copy the CVT-RBv2 mode from https://tomverbeure.github.io/video_timings_calculator#asahi-dev · 2023-04-24 19:15
jannaudo you need anything from the mode except that need to report it to userspace?#asahi-dev · 2023-04-24 19:14
jannauChaosPrincess: I think the algorithm simply breaks down at 2008x60 altogether. it wasn't intended for such extreme aspect ratios#asahi-dev · 2023-04-23 14:44
jannauyou have to follow redirects with -L#asahi-dev · 2023-04-23 14:39
jannauhttps://github.com/AsahiLinux/linux/pull/102.patch https://github.com/AsahiLinux/linux/pull/137.patch but I'm not sure if those apply against asahi-6.2-11 used in the PKGBUILD#asahi-dev · 2023-04-23 14:35
jannauKnedlik: https://paste.debian.net/1278203/ with touchbar_display.patch and touchbar_touchscreen.patch being the changes from the pull request#asahi-dev · 2023-04-23 14:34
jannauso I would try to rebase the the PRs on asahi-6.2-11#asahi-dev · 2023-04-23 14:33
jannauthat makes building the PKGBUILD more complicated#asahi-dev · 2023-04-23 14:30
jannauI'm not sure how well the touchbar PRs rebase against the asahi-6.2-11 kernel so cloning the the asahi kernel tree and the two branches https://github.com/WhatAmISupposedToPutHere/linux would probably a good first step#asahi-dev · 2023-04-23 14:26
jannauthe pkgbuild has support for patches as long as the as they are named *.patch#asahi-dev · 2023-04-23 14:13
jannauadd the patches to the source array, run updpkgsums and makepkg#asahi-dev · 2023-04-23 14:11
jannauhttps://github.com/AsahiLinux/PKGBUILDs/blob/main/linux-asahi/PKGBUILD#asahi-dev · 2023-04-23 14:11
jannaueasiest would probably to add the pull requests as patches to the linux-asahi PKGBUILD#asahi-dev · 2023-04-23 11:54
jannauok, then you need just the kernel with those two pull requests merged #asahi-dev · 2023-04-23 11:52
jannauKnedlik: if you have a m2 based macbook pro you also need to update m1n1 for the touchscreen#asahi-dev · 2023-04-23 11:45
jannauand https://crates.io/crates/input for touchscreen events and generated key events#asahi-dev · 2023-04-23 11:43
jannauif your comfortable or motivated with writing rust you want to use https://github.com/Smithay/drm-rs for the display#asahi-dev · 2023-04-23 11:41
jannauthat is a drm driver for the display and touchscreen driver for the touch input#asahi-dev · 2023-04-23 11:41
jannauChaosPrincess has implemented the HW support needed for the touchbar#asahi-dev · 2023-04-23 11:40
jannaugreat. I think that would be also a good first step for working on the drm driver later#asahi-dev · 2023-04-23 11:38
jannauKnedlik: do you have by any chance a 13" macbook pro? if yes the touchbar daemon might be a good project#asahi-dev · 2023-04-23 11:36
jannauyes, you would need a second computer for it. I have an idea what the timestamps are but it will be certainly helpful to check what macOS does with our hypervisor and tracing for dcp in m1n1:proxyclient/hv/trace_dcp.py#asahi-dev · 2023-04-23 11:34
jannauyou want to look at struct dcp_swap, that one has 3 timestamps#asahi-dev · 2023-04-23 11:33
jannauKnedlik: you have to look drivers/gpu/drm/apple, especially the iomfb* files. that is the part which communicates with the display coprocessor#asahi-dev · 2023-04-23 11:30
jannauchadmed: have you tried how much of the "dcp" power use is the backlight at minimal brightness? use the gpio for the backlight to turn it off. I hope it's minimal though#asahi-dev · 2023-04-23 10:19
jannauthat check wasn't there in 12.x#asahi-dev · 2023-04-23 10:18
jannaumarcan: aided by added verification in the dcp firmware with syslog error prints. after I got the size right it complaining about a surface with size 0x0 at 1920x1080#asahi-dev · 2023-04-22 14:23
jannauI'd start with https://lv2plug.in/pages/developing.html#asahi-dev · 2023-04-22 14:22
jannauKnedlik: development can be in the first step fully independent of any hardware. the plugin gets an audio signal (a stream of samples) and outputs an audio signal. as first you wouldn't necessarily listen to what the plugin does#asahi-dev · 2023-04-22 12:27
jannauyeah! firmware version dependent dcp interfaces in m1n1 as well#asahi-dev · 2023-04-22 12:26
jannauworking, it was setting garbage layer parameters#asahi-dev · 2023-04-22 11:37
jannauso the swap_set_layer_cmd might be interpreted as garbage by dcp#asahi-dev · 2023-04-22 11:36
jannauat least there's a IOMobileFramebuffer::swap_submit_dcp() syslog line#asahi-dev · 2023-04-22 11:35
jannaulooks like the swap_set_layer_cmd had layout/size changes, set_layer succeeds now but swap_end fails#asahi-dev · 2023-04-22 09:35
jannaulooks like there are two new dcp iboot calls in 13.3 but probably appended at the end. 13.2 has already additional calls but swap_set_layer was still working#asahi-dev · 2023-04-22 09:04
jannaudcp 13.3 FW doesn't like m1n1's dcp_ib_swap_set_layer call anymore. other problem problem was that the service init message is now TYPE_REPLY instead of TYPE_NOTIFY#asahi-dev · 2023-04-21 19:46
jannaubut GPU work most likely will become annoying if you develop and test on the same system#asahi-dev · 2023-04-21 19:45
jannauthe bass plugin however shouldn't need a second device#asahi-dev · 2023-04-21 19:44
jannaumany HW related things are annoying to develop/debug if you're using a single device#asahi-dev · 2023-04-21 19:36
jannaua good first step would be to make yourself familiar with m1n1 and https://github.com/AsahiLinux/docs/wiki/Tethered-Boot-Setup-%28For-Developers%29#asahi-dev · 2023-04-19 19:20
jannaufrom my understanding v4l2's stateless m2m codecs would be a good fit api-wise