#asahi-dev · 2023-04-10 11:15
jannaukettenis_: no, it doesn't work but it boots#asahi-dev · 2023-04-10 11:12
jannauchadmed: it trips over the unused pcie port 1. disabling that one is sufficient, enabling port 2 and 3 (ethernet and xhci) causes no issues#asahi-dev · 2023-04-10 10:52
jannaukettenis_: problem is in the hypervisor, works after adding 0x6020 to 'elif chip_id in (0x6021,):'#asahi-dev · 2023-04-10 10:49
jannaudisable all pcie darts#asahi-dev · 2023-04-10 10:35
jannaukettenis_: does m1n1 bring up the secondary cpu cores? fails here on the 10 core j474s#asahi-dev · 2023-04-10 10:23
jannausure, but I don't think we want to use the extra level if it is not necessary#asahi-dev · 2023-04-10 10:09
jannauwe should take's the device's dma mask into account in apple_dart_finalize_domain(), I doubt we need more than 36-bit for most devices#asahi-dev · 2023-04-10 10:06
jannaudoes it work if you limit it to 36 instead of reading DART_T8110_PARAMS3_VA_WIDTH?#asahi-dev · 2023-04-10 10:02
jannaudart-dcp0 has FOUR_LEVELS=0#asahi-dev · 2023-04-10 09:56
jannauI suspect the first level is the ttbr which is flat for dart-t8110#asahi-dev · 2023-04-10 09:55
jannauok, that should fail then too and probably explains the SError OI saw yesterday on the m2 pro mini#asahi-dev · 2023-04-10 09:54
jannauthe dcp/disp0 handling in kboot.c isn't used yet?#asahi-dev · 2023-04-10 09:51
jannauis that the first dart you're looking at?#asahi-dev · 2023-04-09 21:24
jannauwhy apple? "/arm-io/dart-dcp/mapper-dcp" vs. "/arm-io/dart-dcp0/mapper-dcp0" on the m2 pro. will there be a dcp1 on the VR headset, or on the m2 ultra for 10 displays#asahi-dev · 2023-04-09 12:00
jannau3.66 GHz vs. 3.5 GHz#asahi-dev · 2023-04-09 11:56
jannauthe 16" m2 max has a high performance mode with a higher max frequency#asahi-dev · 2023-04-09 11:39
jannaudieX is just stuff which is on both m1 ultra dies, behaves like the die0 include if included with DIE 0 defined#asahi-dev · 2023-04-09 11:36
jannau+to#asahi-dev · 2023-04-09 11:36
jannauprobably not the first priority fix after copying the t600x devicetrees#asahi-dev · 2023-04-09 11:32
jannauI think kettenis_ or chadmed have started with devicetrees#asahi-dev · 2023-04-09 11:31
jannauthe m2 or m2 pro mac mini (or both) came with 13.0-special#asahi-dev · 2023-04-09 11:30
jannauah, yes, mine came with 13.0-special as well. I forgot that#asahi-dev · 2023-04-09 11:28
jannauone reason for 13.2 would be that the 2023 devices will probably ship for a while with 13.2. the installer would work without update. otoh most would probably update on first run#asahi-dev · 2023-04-09 11:25
jannauthere is t6500 without known use#asahi-dev · 2023-04-09 11:25
jannaulooking macos 13.3? I was wondering if we want use to 13.3.1 for the 2023 devices. I'm sure the dcp firmware interface is very close if not identical#asahi-dev · 2023-04-09 11:06
jannauok, I'll prepare everything I have. for m1n1 work it's mostly the 13.2 tracing and the dptx implementation for m1n1#asahi-dev · 2023-04-09 10:18
jannaualso are the annotations for ActiveRegion correct? "max_x max_y min_w max_w"? any idea how they work?#asahi-dev · 2023-04-09 10:04
jannaumarcan: are you looking into dcp? I have hackish ipc changes for 12.3 / 13.2 FW coexisting#asahi-dev · 2023-04-09 09:36
jannauChaosPrincess: yes, hopefully not much work to support (at least without 6GHz support)#asahi-dev · 2023-04-09 09:32
jannauthe devicetree for the m2 mini is already submitted for upstream and except for display, wlan and bt everything works#asahi-dev · 2023-04-09 09:30
jannaujust because you don't see code changes means there are none#asahi-dev · 2023-04-09 09:30
jannauthe device is public for 2 1/2 months, anything before that is useless to use. we can't add support based on rumors#asahi-dev · 2023-04-08 16:35
jannau3 reboots, 3 times with working nic. was consistently broken before#asahi-dev · 2023-04-08 16:31
jannaubooting from disk works now as well. so apparently a heisenbug#asahi-dev · 2023-04-08 16:29
jannauHV/chainloading m1n1 + u-boot with the asahi kernel on disk works as well#asahi-dev · 2023-04-08 16:19
jannausigh, works now with asahi-wip under HV and chainloaded, with some minor modifications in the port setup#asahi-dev · 2023-04-08 16:09
jannauno change with m1n1 v1.2.5#asahi-dev · 2023-04-08 16:04
jannaumaybe c6c426581b in m1n1 1.2.6#asahi-dev · 2023-04-08 15:59
jannauasahi (asahi-6.2-11) fails as well. not unexpected looking at the source changes but I'm quite sure I tested it#asahi-dev · 2023-04-08 15:54
jannaups_apcie_gp_sys is already always-on#asahi-dev · 2023-04-08 15:52
jannaupd_ignore_unused doesn't help, I'll try to make the pd always on#asahi-dev · 2023-04-08 15:48
jannauthere is only a single power-domain for pcie and nothing port specific. the other ports work#asahi-dev · 2023-04-08 15:46
jannaufails with asahi-dev#asahi-dev · 2023-04-08 15:46
jannauu-boot still uses 100ms as timeout#asahi-dev · 2023-04-08 15:46
jannauport setup in u-boot is identical except that u-boot polls the link status instead of waiting for the link up irq#asahi-dev · 2023-04-08 15:38
jannaumarcan: studio#asahi-dev · 2023-04-08 12:21
jannauworks reliable in u-boot's pcie setup probe#asahi-dev · 2023-04-08 12:20
jannauthe aquantia nic's pcie link doesn't seem to come up anymore (with asahi-6.2-12 and asahi-wip)#asahi-dev · 2023-04-07 11:38
jannauwhich calls pci_bus_add_devices(), this doesn't look sound but not entirely clear what breaks the link#asahi-dev · 2023-04-07 10:56
jannauyes, it is something linux does. the link for the xhci port is reported as up before calling pci_host_common_probe()