#asahi-dev · 2026-01-27 11:08
jannaunvidias kernel and user space driver work on the mac pro, I'd expect they work via thunderbolt as well#asahi-dev · 2026-01-27 11:07
jannauthe mac pro is supported except for the main installer since the fedora images are too old. Will be fine with Fedora 43#asahi-dev · 2026-01-27 11:06
jannauthe base m3 macbook pro and the m3 imacs are still using i2c usb-pd controllers#asahi-dev · 2026-01-27 11:05
jannauisp/webcam can probably a optional initial feature as well for m3 devices#asahi-dev · 2026-01-27 08:59
jannaufeel free to pick stuff from https://github.com/jannau/linux/tree/t8122-j504 where the untested / unadjusted dt-bindings device nodes are#asahi-dev · 2026-01-27 08:57
jannauthe latter should also work in asahi-wip. The m3 branch is merged#asahi-dev · 2026-01-27 08:56
jannaumake dtbs_check should not produce any warnings in that branch. if you want to test just a single device tree you can use `make O=_checkdtb CHECK_DTBS=y apple/t8122-j504.dtb`#asahi-dev · 2026-01-27 08:54
jannaunoopwafel: I've pushed a basic t8122 devicetree to https://github.com/AsahiLinux/linux/tree/bits/001-devicetree-m3#asahi-dev · 2026-01-26 19:35
jannauthe main.py needs to be modified to be able to use the installer at least for fw extraction#asahi-dev · 2026-01-26 19:34
jannauusing https://github.com/AsahiLinux/asahi-installer/blob/main/asahi_firmware/wifi.py to extract the files#asahi-dev · 2026-01-26 19:27
jannaunoopwafel: did you look up the correct identifer? did you extract the full set of files with a modified installer? how does it fail? note that it tries to load the most specific file and drops suffixes. Each non-existing file is logged#asahi-dev · 2026-01-26 00:01
jannauerr, no. I was looking at the m4 iMacs#asahi-dev · 2026-01-25 23:36
jannaubut at least the template adt has 4 complete usb4 ports including all including acio, apciec, dpphy, dpin[01] and dpxbar#asahi-dev · 2026-01-25 23:32
jannauhttps://support.apple.com/en-us/117734 just mentions 1 external display and 2 usb4 and 2 usb3.1 ports#asahi-dev · 2026-01-25 23:28
jannauno, but to be fair the other devices are laptops#asahi-dev · 2026-01-25 23:25
jannauhuh, the base m3 has 4 SoC USB4 ports and 2 dcpext if installed in an imac#asahi-dev · 2026-01-25 23:02
jannaunew dt-bindings (or significant changes) should be send upstream first#asahi-dev · 2026-01-25 23:01
jannauack, I was thinking of just adding the new soc compatibles required to make make dtbs_check pass. we could even require to those simple dt binding changes as commits and only merge dt changes if make dtbs_check passes for m3+#asahi-dev · 2026-01-25 22:51
jannauand ensure that we send out patches quickly#asahi-dev · 2026-01-25 22:49
jannauI think it's acceptable if we require upstreamable commits#asahi-dev · 2026-01-25 22:48
jannauI'm not sure that upstream first is a practical idea for device trees#asahi-dev · 2026-01-25 22:47
jannauit seems to be a little cumbersome to have these distributed trees#asahi-dev · 2026-01-25 22:46
jannauI'm wondering whether we should start adding the t8122 dt to the downstream kernel#asahi-dev · 2026-01-25 14:44
jannauthe same for j473, j314c, j375d#asahi-dev · 2026-01-25 14:41
jannauj274 has interrupts and enable-sw-drain = 1#asahi-dev · 2026-01-25 14:34
jannaunot sure why the one I paste has none. looked at a few others and they have all interrups#asahi-dev · 2026-01-25 14:31
jannauj493 has an interrupt in dockchannel-uart#asahi-dev · 2026-01-25 13:58
jannausven: since I already prepated that: https://paste.debian.net/hidden/c8d41c53#asahi-dev · 2026-01-25 11:20
jannauintegralpilot: I'm still puzzled why you need `nonposted-mmio;`#asahi-dev · 2026-01-25 10:45
jannauit has disjoint regs from dockchannel-mtp and no interrupt or phandle#asahi-dev · 2026-01-25 10:44
jannauI don't even understand how dockchannel-uart is supposed from the ADT#asahi-dev · 2026-01-25 10:41
jannauit's not handled automatically for multiple domains since the ordering / timing could be device specific#asahi-dev · 2026-01-25 10:40
jannaunoopwafel: devm_pm_domain_attach_list#asahi-dev · 2026-01-25 10:34
jannaumaybe aop? the dockchannel-uart node has a 'max-aop-clk' property#asahi-dev · 2026-01-25 10:30
jannaubut I think those are more status flags for mailbox queues than an interrupt controller#asahi-dev · 2026-01-25 10:29
jannauif you chain devices on like for dockchannel downstream an irq controller is good fit#asahi-dev · 2026-01-25 10:19
jannauit wasn't just the atomic context. mailbox was overall a bad fit for asc: https://lore.kernel.org/asahi/20230328-soc-mailbox-v1-0-3953814532fd@marcan.st/#asahi-dev · 2026-01-25 10:13
jannauand dockchannel looks like a mailbox to me as well#asahi-dev · 2026-01-25 10:13
jannaumy first guess is mtp stands for is multi touch processor#asahi-dev · 2026-01-24 22:25
jannauit uses 8-bit and it uses software cursors with dual displays#asahi-dev · 2026-01-24 22:21
jannaukwin does not use ARGB2101010 for cursors now that it is available?#asahi-dev · 2026-01-24 22:16
jannauI wanted to force sRGB for 8-bit RGB formats but I forgot. I think that would solve the oversaturated colors on TTYs#asahi-dev · 2026-01-24 22:14
jannauthe solution for the problem for SDR is using a color profile. The only reason kwin dowsn't use the internal one by default is that displays with broken color space information are not uncommon#asahi-dev · 2026-01-24 22:12
jannauto my understanding oversaturated colors are expected for the Default colorspace with wide gamut displays and without active color profile (at least not uncommon)#asahi-dev · 2026-01-24 22:10
jannauI did not look into external displays yet but for the internal mini led display selecting Display P3 as icc profile has the same result as using dcp's sRGB colorspace#asahi-dev · 2026-01-24 22:06
jannauI thought you wanted sRGB primarily for the internal displays as those are oversatuted#asahi-dev · 2026-01-24 19:44
jannaufl0_id__: I use https://paste.centos.org/view/faaef47f#asahi-dev · 2026-01-24 19:37
jannauI've pushed asahi-6.18.7-1 to github with dcp fixes, a rust compile fix and small preparations for m3/m4#asahi-dev · 2026-01-24 13:55
jannau I haven't looked at pcie. maybe also additional power states as nmve and pcie are closely related. pcie physical layer is used to connect the actual NAND chips (but not using PCIe as protocol)#asahi-dev · 2026-01-24 13:43
jannaunot sure about the exact error but it can be also caused by the HW block being powered down