#asahi-dev · 2021-11-08 10:31
kettenisso a "read" packet#asahi-dev · 2021-11-08 10:31
kettenisthe packet I'm actually interested is, is one that starts with 0x20#asahi-dev · 2021-11-08 10:29
kettenisis that the packet crc failing? or the message crc?#asahi-dev · 2021-11-08 10:23
kettenisstill fighting with the new AIC?#asahi-dev · 2021-11-08 09:20
kettenisyes, it is effectively a fifo fill level#asahi-dev · 2021-11-08 09:18
kettenisalthough I didn't investigate that bit thoroughly#asahi-dev · 2021-11-08 09:18
kettenisthat does indeed appear to be the case#asahi-dev · 2021-11-05 14:09
kettenisnot sure if there is space in nvram for us to scribble in though#asahi-dev · 2021-11-05 14:09
kettenisit should be possible to isolate nvram access from the OS in a fairly reliable way on this hardware#asahi-dev · 2021-11-05 14:08
kettenismaybe we can do something clever there for these systems#asahi-dev · 2021-11-05 13:59
kettenisagraf: yes, the lack of runtime access to UEFI variables does stand in the way of supporting multi-booting non-macOS OSes#asahi-dev · 2021-11-05 11:02
kettenisscenario b) is really there such that people can upgrade their kernel after updating m1n1 and the device tree#asahi-dev · 2021-11-05 11:01
kettenison the other hand, the machine is usable with only the snps,dwc3 matching, so maybe that is good enough#asahi-dev · 2021-11-05 09:59
kettenis(I know I argued against it earlier)#asahi-dev · 2021-11-05 09:59
kettenisor maybe we should have an apple,dwc3 compatible after all#asahi-dev · 2021-11-05 09:58
kettenisso if we already know that t6000 needs the same reset quirk as the t8103 it is probably best to make that explicit#asahi-dev · 2021-11-05 09:57
kettenisbut if we then remove the t8103 compatible from the DT for the t6000, an older kernel would no longer work properly with the new DT#asahi-dev · 2021-11-05 09:56
kettenisif we list both t6000 and t8103 as compatible for the t6000 we can support the quirk easily and only apply it to t6000#asahi-dev · 2021-11-05 09:55
kettenissuppose we find a new quirk that only applies to t8103 but breaks the t6000#asahi-dev · 2021-11-05 09:54
kettenisb) running an older kernel with a newer DT#asahi-dev · 2021-11-05 09:54
kettenisa) running a new kernel with an older DT#asahi-dev · 2021-11-05 09:53
kettenisso there are two cases to consider:#asahi-dev · 2021-11-05 09:51
kettenisso in that sense it is ok#asahi-dev · 2021-11-05 09:51
kettenisI guess you'd still be able to quirk t6000 and t8103 separately in that case#asahi-dev · 2021-11-05 09:48
kettenissven: I don't think the t6000 dwc3 should have t8103 as a compatible#asahi-dev · 2021-11-05 09:43
kettenisdual booting macOS will work just fine#asahi-dev · 2021-11-05 09:42
kettenisand the installation experience is really not different from an x86 machine with UEFI#asahi-dev · 2021-11-05 09:41
kettenisbut now that's done, the only thing that's needed is to have m1n1 with a u-boot payload and some free space#asahi-dev · 2021-11-05 09:40
kettenisagraf: we did teach the OpenBSD installer to preserve the essential Apple partitions#asahi-dev · 2021-11-04 21:42
kettenisif it is a packet that starts with a 0x20 byte, I'd be interesting in seeing it fully#asahi-dev · 2021-11-04 21:36
kettenisdon't think I'm seeing packets that fail the crc16 check unless I do something wrong#asahi-dev · 2021-11-04 21:34
kettenisI think one of them is a proper HID report packet#asahi-dev · 2021-11-04 21:34
kettenisyes, I see some weird packets#asahi-dev · 2021-11-04 15:18
kettenisI may have sent that message to the wrong devicetree mailing list#asahi-dev · 2021-11-04 15:17
kettenismight as well#asahi-dev · 2021-11-04 13:00
kettenisbut at least for honshu the antenna sku doesn't seem to matter#asahi-dev · 2021-11-04 12:50
kettenishmm, it appears that it isn't#asahi-dev · 2021-11-04 11:59
kettenisthat bit isn't encoded in the OTP?#asahi-dev · 2021-11-04 11:06
kettenisthe hard bit is to come up with a sensible property name and where to define the binding for it ;)#asahi-dev · 2021-11-04 11:06
ketteniswe already add a "local-mac-address" property to the wifi pcie device node, so this isn't too difficult#asahi-dev · 2021-11-04 11:04
kettenismarcan: so we need to transplant the "module-instance" property from the ADT into the device tree#asahi-dev · 2021-11-04 10:55
kettenisu-boot provides its own UEFI implementation#asahi-dev · 2021-11-04 10:55
kettenisno, there is no edk2 involved on the m1 macs#asahi-dev · 2021-11-04 10:52
kettenisno reason u-boot couldn't do the same#asahi-dev · 2021-11-04 10:52
kettenisedk2 provides http boot, where you can point it directly at an ISO image and boot it#asahi-dev · 2021-11-04 10:51
ketteniswell, you have to start somewhere ;)#asahi-dev · 2021-11-04 10:48
kettenisI just commit stuff and within 24 hours Theo has built a new snapshot with it enabled ;)#asahi-dev · 2021-11-04 10:47
kettenisyeah, I don't have to worry about that for OpenBSD#asahi-dev · 2021-11-04 10:23
kettenishave a generic UEFI install option for Debian/Ubuntu/SuSE/OpenBSD and another option for the ALARM-based distro that marcan has proposed#asahi-dev · 2021-11-04 10:21
kettenisanayway, there is no reason the Asahi installer couldn't do both