#asahi-dev · 2025-09-21 16:56
nickchanthere's still a regression in adt_is_compatible()#asahi-dev · 2025-09-21 14:20
nickchan{0x5ac8012, 0x824606}; <- this gives "Debug USB"#asahi-dev · 2025-09-21 14:18
nickchanand that gives swd but it's not particlarly useful on production devices#asahi-dev · 2025-09-21 14:18
nickchanthere's also a vdm commands that gives a USB PID of 0x1881 i think#asahi-dev · 2025-09-21 14:17
nickchanhowever t2 mac cannot serve as a host with macvdmtool#asahi-dev · 2025-09-21 14:17
nickchan(for macvdmtool)#asahi-dev · 2025-09-21 14:17
nickchanit works as both a target and host#asahi-dev · 2025-09-21 14:16
nickchanjannau: works on m2 ipad at least#asahi-dev · 2025-09-21 14:10
nickchanit can be used to control a t2 target however only reboot and dfu will work#asahi-dev · 2025-09-21 10:28
nickchanlinux driver causes the kernel boot to be frozen on t2 (actually frozen not just the screen); guess I should try m1n1's touchbar bad apple#asahi-dev · 2025-09-21 07:59
nickchan0x87a = 2170 and 0x3c = 60; so at least ADP_SCREEN_SIZE is the same and this is not the case on A11#asahi-dev · 2025-09-21 07:59
nickchan>>> read32(u.adt["/arm-io/disp0"].get_reg(2)[0] + 0xc) 0x87a003c#asahi-dev · 2025-09-21 07:54
nickchant2's display play reg layout in adt is similar to m1 dfr too#asahi-dev · 2025-09-21 07:53
nickchani probably should investigate #asahi-dev · 2025-09-21 07:53
nickchan(in adt)#asahi-dev · 2025-09-21 07:53
nickchanthis is suspicious the reg layout of a9 and a10's display pipe is more similar to m1's dfr display pipe than a11's display pipe#asahi-dev · 2025-09-20 11:24
nickchannot like they are used on anything other than apple devices#asahi-dev · 2025-09-20 11:24
nickchanfound the codenames of the pmics in iphone maybe i should change the compatible to match the style of current apple silicon mac pmic instead of using dlg,da2XXX (they are designed by dialog semiconductor)#asahi-dev · 2025-09-16 13:03
nickchanmust be a leftover from when m1 is everything#asahi-dev · 2025-09-16 13:02
nickchansven: it's not a big deal but "usb: dwc3: Add Apple Silicon DWC3 glue layer driver" in the wip/atcphy branch mentions Apple M1 specifically which is probably not appropriate#asahi-dev · 2025-09-16 12:59
nickchana11 and t2 spmi series should be ready again now after the generic compatible incident#asahi-dev · 2025-09-16 12:48
nickchanthat i have no idea how to drive yet#asahi-dev · 2025-09-16 12:48
nickchannow there's also usb3 phys on some a9x and a10x ipads but as far as I can tell that's a completely different animal#asahi-dev · 2025-09-16 12:44
nickchanit also has complications of dealing with 32-bit dma devices but without a dart#asahi-dev · 2025-09-16 12:42
nickchansven: correct there's some similarities but not enough to use one driver for both#asahi-dev · 2025-09-15 14:25
nickchanjannau: ah then im mistaken#asahi-dev · 2025-09-15 14:11
nickchanerm actually dart in general would be broken on t8103#asahi-dev · 2025-09-15 14:11
nickchancause that code matches against dart,t8020#asahi-dev · 2025-09-15 14:11
nickchanin that case the dart lock code must be broken right now on t8103#asahi-dev · 2025-09-15 14:02
nickchanand i don't know about rust to fix that#asahi-dev · 2025-09-15 13:58
nickchanthis is a bug#asahi-dev · 2025-09-15 13:58
nickchanso like calling adt_is_compatible(adt, offset, "usb-complex,s5l8960x") on a node that has a compatible property of usb-complex,t8012\0usb-complex,s5l8960x\0 doesn't match anymore#asahi-dev · 2025-09-15 13:52
nickchanchadmed: the new adt_is_compatible() doesn't match against fallback compatibles i think#asahi-dev · 2025-09-15 09:25
nickchanmaz on a11 and m2 it's 0x8444c004 in HW... looks more like a workaround to me#asahi-dev · 2025-09-15 08:14
nickchanbut why?#asahi-dev · 2025-09-15 08:13
nickchanon t6000 ctr_el0 is 0x84448004 but in a vm under macos xnu seems to trap it and become 0x8444c004#asahi-dev · 2025-09-15 01:54
nickchan...and of course the mail server returns error at this moment in any case it's finally sent#asahi-dev · 2025-09-15 01:25
nickchanhopefully not too much friction in that one#asahi-dev · 2025-09-15 01:25
nickchanconceptually the dt-binding patch is pretty much the same thing as the t602x spmi dt-binding patch #asahi-dev · 2025-09-15 01:23
nickchanokay, the spmi changes are picked up probably going to reroll my spmi patches soon#asahi-dev · 2025-09-08 11:00
nickchanin v1 so not the same case#asahi-dev · 2025-09-08 11:00
nickchanah alright then was looking at how FEAT_PMUv3 in kvm series is handled but it turns out that series did have some discussion about how things to be taken #asahi-dev · 2025-09-08 10:41
nickchan(currently on v8 resend)#asahi-dev · 2025-09-08 10:41
nickchanthere's some addressed review comments on v7's resend https://lore.kernel.org/asahi/20250616-apple-cpmu-v7-0-df2778a44d5c@gmail.com/#asahi-dev · 2025-09-08 10:41
nickchanmaz: this might be stretching it but do you think you can take a7-a11's cpu pmu (patch 1-12) through kvmarm? it is your driver and you actually have apple silicon hardware after all. if one squint really hard then patch 2 mentions EL2 so it's not /completely/ off-topic: https://lore.kernel.org/asahi/20250908-apple-cpmu-v8-0-d83b4544dc14@gmail.com/#asahi-dev · 2025-09-06 09:26
nickchanI mean SARTv0#asahi-dev · 2025-09-06 09:26
nickchanso... I guess the SARTv1 commit is staying as-is?#asahi-dev · 2025-09-01 03:26
nickchan(also adding back the newlines and dropping tags on bindings)#asahi-dev · 2025-09-01 03:26
nickchanokay I will wait a bit before reolling the spmi stuff #asahi-dev · 2025-08-28 15:57
nickchananyways this whole dt mess means I will have to rebase my spmi dt patches on top of your series and i probably will do that later when there's more reviews on your series