#asahi-dev · 2021-11-13 17:43
jeffmiwI was trying to avoid hard coded value, like you did for the aic_base for aic2#asahi-dev · 2021-11-13 17:43
jeffmiwok I'll submit the pr with just that then#asahi-dev · 2021-11-13 17:42
jeffmiwmacos works with 8000#asahi-dev · 2021-11-13 17:42
jeffmiwif we do not "trust" or do not want to use the adt value#asahi-dev · 2021-11-13 17:42
jeffmiwok, that is even easier#asahi-dev · 2021-11-13 17:41
jeffmiwso you prefer to use hard coded value than the adt one ?#asahi-dev · 2021-11-13 17:39
jeffmiwyes aic1#asahi-dev · 2021-11-13 17:39
jeffmiwmacos is hitting 0x5024 which is above 0x4000#asahi-dev · 2021-11-13 17:38
jeffmiwthen I realized we are currently using 3 different values :) 0x4000 in aic.h, 0x8000 in .dtsi, and adt has 0xC000 :)#asahi-dev · 2021-11-13 17:37
jeffmiwI will submit a pr to fix it, just trying to make it more "aligned" in aic.c using also values from adt#asahi-dev · 2021-11-13 17:36
jeffmiwok, it is just that with aic2 changes, m1n1 hv.py is using the adt values for base and size, but the aic.c is using base from adt and size is hard coded to a smaller value of 0x4000 resulting in an HV IPA not mapped if you trace irqs when running macos under the hv#asahi-dev · 2021-11-13 17:26
jeffmiwhumm ok. thx.#asahi-dev · 2021-11-13 17:14
jeffmiwdoes anyone know why we have a register length of 0x8000 for the aic in the t8103.dtsi while adt has it at 0xC000 for the M1 and another value for aic2 (likely 0x1000 if the m1n1 define is correct) ?#asahi-dev · 2021-10-24 20:04
jeffmiwdma is more because of the trackpad than the keyboard in my opinion#asahi-dev · 2021-10-23 19:16
jeffmiwand this is the "simple" version with no dma. If you want to do it the macos way, you need sio/dart-sio also ..#asahi-dev · 2021-10-23 19:11
jeffmiwspi/gpio/clock/aic#asahi-dev · 2021-10-23 19:10
jeffmiwkettenis: what is bothering you with the keyboard stuff ?#asahi-dev · 2021-10-22 20:43
jeffmiwyes it does#asahi-dev · 2021-10-22 19:59
jeffmiwI have a mba, is there anything you need to be tested with this branch ?#asahi-dev · 2021-10-22 19:57
jeffmiwalyssa: thanks, mu-one branch 20211022 boots now without the mailbox issue.#asahi-dev · 2021-10-21 21:35
jeffmiwit seems it needs more than that or I screwed it. I'll spend more time on it tomorrow.#asahi-dev · 2021-10-21 21:17
jeffmiwj_ey: thanks, that rings some bell, let me give it a try#asahi-dev · 2021-10-21 21:15
jeffmiw2021015 branch was booting fine#asahi-dev · 2021-10-21 21:15
jeffmiwI'm on mba#asahi-dev · 2021-10-21 21:15
jeffmiwalyssa: using your mu-one/20211018 branch, I'm getting an early kernel crash "Unable to handle kernel NULL pointer" in mbox_request_channel during dcp_platform_probe/rtkit_init. Before digging into it, just want to check if it is known.#asahi-dev · 2021-03-21 18:36
jeffmiwI do not know if I can do a USB C to USB C loop on a Linux PC#asahi-dev · 2021-03-21 18:36
jeffmiwI do not know if I can do a USB C to USB C loop on a Linux PC#asahi-dev · 2021-03-21 18:36
jeffmiwI never used those cables before, I do not have any USB-C devices to try them with something else#asahi-dev · 2021-03-21 18:36
jeffmiwI never used those cables before, I do not have any USB-C devices to try them with something else#asahi-dev · 2021-03-21 18:35
jeffmiwif I use my USB-C to USB-C cables (I have 2 supposed to be superspeed) I can't get them to work ...#asahi-dev · 2021-03-21 18:35
jeffmiwif I use my USB-C to USB-C cables (I have 2 supposed to be superspeed) I can't get them to work ...#asahi-dev · 2021-03-21 18:34
jeffmiwI can get it to work on the first USB port then switch to the 2nd one, but not more than once#asahi-dev · 2021-03-21 18:34
jeffmiwI can get it to work on the first USB port then switch to the 2nd one, but not more than once#asahi-dev · 2021-03-21 18:34
jeffmiwif I boot with cable unplugged, once I plug it, it works once#asahi-dev · 2021-03-21 18:34
jeffmiwif I boot with cable unplugged, once I plug it, it works once#asahi-dev · 2021-03-21 18:33
jeffmiwworks mean I have USB enum on my Linux PC and I can get the shell.py connecting#asahi-dev · 2021-03-21 18:33
jeffmiwworks mean I have USB enum on my Linux PC and I can get the shell.py connecting#asahi-dev · 2021-03-21 18:33
jeffmiwusing my USB-C to USB-A + USB-A to USB C, it works 5/5 with cable plugged before botting#asahi-dev · 2021-03-21 18:33
jeffmiwusing my USB-C to USB-A + USB-A to USB C, it works 5/5 with cable plugged before botting#asahi-dev · 2021-03-21 18:30
jeffmiwsven: I have used your branch usb-uartproxy-console-wip on my macbk air, m1n1 stored on the disk(linux partition), here are the results of my test:#asahi-dev · 2021-03-21 18:30
jeffmiwsven: I have used your branch usb-uartproxy-console-wip on my macbk air, m1n1 stored on the disk(linux partition), here are the results of my test:#asahi-dev · 2021-03-16 21:29
jeffmiwsven: ok I'll try that. Yes I have to store it with kmutil. no chance to play that much with it yet ..#asahi-dev · 2021-03-16 21:29
jeffmiwsven: ok I'll try that. Yes I have to store it with kmutil. no chance to play that much with it yet ..#asahi-dev · 2021-03-16 21:29
jeffmiwsven: ok I'll try that. Yes I have to store it with kmutil. no chance to play that much with it yet ..#asahi-dev · 2021-03-15 22:22
jeffmiwyes this is not making sense to me either ... I must be missing something ...#asahi-dev · 2021-03-15 21:00
jeffmiwnow it is working all the time: I can get to shell and chainload no problem ... I must have done something wrong previously ...#asahi-dev · 2021-03-15 20:59
jeffmiwboth with usb and fb I'm all set to dig further :)#asahi-dev · 2021-03-15 20:59
jeffmiwI'll do more testing to see if I can figure someting out#asahi-dev · 2021-03-15 20:58
jeffmiwwhat I figured out is that I need to use my type C to type usb A then my usb B to C.. tried my 2 usb C to C cables none worked#asahi-dev · 2021-03-15 12:48
jeffmiwsven: it seems I just have instabilities with my setup, I was able to get the proxy shell once, sometimes I do not get the usb enum. now I have the usb&fb I'll try to reproduce and fix