#asahi-dev · 2024-03-17 20:58
jannegI've sent the BOOTSTD conversion out today#asahi-dev · 2024-03-17 20:57
jannegI would have expected that a fedora user would have run into bti in llvmpipe before#asahi-dev · 2024-03-17 20:55
jannegkettenis: ignoring the interaction with CMD_BOOTEFI_BOOTMGR the Boot####/BootOrder seeding still works but I was thinking if we shouldn't replace that with an #asahi-dev · 2024-03-17 20:51
janneghuh, I wasn't aware that llvmpipe was broken with bti#asahi-dev · 2024-03-14 12:41
jannegI didn't get that far as my tests with v2024.04-rc4 / BOOTSTD_FULL / !DISTRO failed because "BootOrder" is already defined#asahi-dev · 2024-03-14 12:39
jannegthe snprintf/utf8_utf16_strcpy in efi_seed_boot_options() but I see now that I missed `u16 *tmp = devname;`#asahi-dev · 2024-03-14 11:35
jannegkettenis: the EFI boot options code has in principle the same problem but if I don't miss anything it is dead code#asahi-dev · 2024-03-12 19:07
jannegyes, u-boot wants hex partition numbers even when `nvme part 0` prints base 10 numbers#asahi-dev · 2024-03-12 19:05
jannegkettenis: https://paste.centos.org/view/449442b7 explains why some test installs failed to load the xhci firmware#asahi-dev · 2024-03-12 19:04
jannegmps: builds here with llvm 17#asahi-dev · 2024-03-12 10:22
jannegrust 1.75 compiles asahi-wip-6.8 on fedora#asahi-dev · 2024-03-11 22:53
jannegfix send#asahi-dev · 2024-03-11 22:39
jannegSPI keyboard issue fixed in https://github.com/jannau/linux/commit/792462eb5dc3c014463b668ba232350f326b09ab#asahi-dev · 2024-03-11 22:00
jannegthanks, feel free to use that as workaround while I search for the issue. already helpful to confirm my suspicion of the cause#asahi-dev · 2024-03-11 21:44
jannegrevert of 4d8ff6b0991d5 "spi: Add multi-cs memories support in SPI core" seems to fix it#asahi-dev · 2024-03-11 21:38
jannegM1* SPI keyboard/trackpad appears to be broken#asahi-dev · 2024-03-11 21:34
jannegaxboe: looking into it, issue seems not to reprodruce M1 max macbook pro. can you test if https://paste.centos.org/view/f5069e2d fixes it. It will disable the HDMI port#asahi-dev · 2024-03-11 20:12
jannegmps: that's what the upstream kernel reports. I don't think we've modified that ever even when there was support for later versions#asahi-dev · 2024-03-11 20:06
jannegchadmed claimed that rust 1.74 worked on gentoo#asahi-dev · 2024-03-11 20:01
janneg1.75 worked for 6.6-15 and I don't remember a thing which could have broken that#asahi-dev · 2024-03-11 19:59
jannegalso new firmware/compatible string for ascwrap (v6 vs. v4), I haven't checked if that's a firmware or m3 thing though#asahi-dev · 2024-03-11 19:57
jannegif only apple had a 13.5/13.6 ipsw for it#asahi-dev · 2024-03-11 19:52
jannegmps: this is still early testing. rust 1.75 might work as well#asahi-dev · 2024-03-11 19:50
jannegaxboe: probably the double iommu from the panel and HDMI port, this is annoying to test for me since the macbook pro in use. use nomodeset for for basic framebuffer support#asahi-dev · 2024-03-11 11:50
janneg indeed, https://github.com/jannau/linux/tree/beta-6.8/asahi-wip#asahi-dev · 2024-03-11 11:44
janneglightly tested on multiple devices#asahi-dev · 2024-03-11 11:44
jannegasahi kernel rebase onto v6.8 pushed to https://github.com/jannau/linux/tree/beta-6.8/asai-wip (beta-6.8/base and beta-6.8/bits/*)#asahi-dev · 2024-03-09 21:29
jannegI'm hitting a EL1 translation fault in _start. I guess I should replace the 1st m1n1 with one which parses boot_args correctly#asahi-dev · 2024-03-09 21:23
jannegbooting just the 4 perf cpus works as well#asahi-dev · 2024-03-09 21:15
jannegI guess the next step should be to fix the hypervisor (was it working for dberlin on t603x?) and then to find out how "iop,ascwrap-v6" differs from "iop,ascwrap-v4"#asahi-dev · 2024-03-09 21:12
jannegat least it boots with `maxcpus=1` until it tries to mount the root fs#asahi-dev · 2024-03-09 21:04
jannegthe boot cpu (4, first perf core) and only that has "{clock,memory,bus,peripheral,fixed,timebase}-frequency = 24000000;" in it's ADT node#asahi-dev · 2024-03-09 20:59
jannegI've remembered that when I read the link#asahi-dev · 2024-03-09 20:58
jannegbut is M3 (partially) 8.6?#asahi-dev · 2024-03-09 20:51
janneghmm, https://developer.arm.com/documentation/ka005374/latest/#asahi-dev · 2024-03-09 20:48
jannegin m1n1#asahi-dev · 2024-03-09 20:48
jannegthat is after "correcting" CNTFRQ_EL0 to 24 MHz on the efficiency cores#asahi-dev · 2024-03-09 20:46
jannegsigh, apparently iboot configures CNTFRQ_EL0 correctly: https://paste.debian.net/1310072/#asahi-dev · 2024-03-09 11:22
janneganne#asahi-dev · 2024-03-09 09:22
jannegchadmed: did it improve with 6.0.1? there was a bug letting it commit the pageflip later than intended. That has improved things here but not fully fixed it. dcp is still acting in an unexpected way#asahi-dev · 2024-03-08 21:31
janneglooks like linux might not expect booting from cpu != 0 either#asahi-dev · 2024-03-08 21:30
jannegcpu 0: 0, 1-3: 1000000000 and 4-7: 24000000#asahi-dev · 2024-03-08 21:04
jannegvalue seems to be written by iboot on purpose though: 1000000000#asahi-dev · 2024-03-08 21:01
janneglinux isn't particularly happy: "CPU features: SANITY CHECK: Unexpected variation in SYS_CNTFRQ_EL0. Boot CPU: 0x000000016e3600, CPU1: 0x0000003b9aca00"#asahi-dev · 2024-03-08 20:56
jannegnot much to show yet except replicating/verifying dberlin's work#asahi-dev · 2024-03-08 20:40
janneg.revision/.version are of course unmodified#asahi-dev · 2024-03-08 20:38
jannegsigh even#asahi-dev · 2024-03-08 20:32
jannegsign, for some reason the boot_args on m3 are at least 416 bytes larger. mem_size_actual seems to be at 0x478 instead of 0x2d8#asahi-dev · 2024-03-04 14:14
jannegm3 macbook airs but no m3 mac mini. I guess/hope that will be released with the mac studio#asahi-dev · 2024-03-03 12:08
jannegthat would be extreme for 165Hz, try 3 or 4 ms