#asahi · 2021-08-06 08:27
pipcet[m]yes, that's the trouble#asahi · 2021-08-06 08:27
pipcet[m]sven: is it possible we get a "proper" SMC notification? I just got those to work...#asahi · 2021-08-06 08:26
pipcet[m]arguably, it might make sense to let macos initialize the hardware, then kill it and run Linux instead using initialized hardware, but I think it's way more trouble than any benefit we might see...#asahi · 2021-08-06 08:22
pipcet[m]oh. that makes sense, sorry. I have a MBP :-)#asahi · 2021-08-06 08:16
pipcet[m]arnd: even sharing just USB is hard because the interrupt controller isn't designed to be shared and the two USB ports (their PD chips) share an IRQ line..#asahi · 2021-08-06 08:15
pipcet[m]arnd: I did something like that, communicating using "shared" memory (actually magic changing signatures in RAM that linux found and overwrote with its data)#asahi · 2021-08-03 18:28
pipcet[m]oooh, thanks!#asahi · 2021-08-03 18:19
pipcet[m]marcan: oh, apple never told me that behind the URL they gave me ;-)#asahi · 2021-08-03 18:15
pipcet[m]yeah, I'm beginning to wish I had gotten two of them so I could use one and hack on the other (also it would have been really handy that time I ended up putting my machine into I-need-DFU mode)#asahi · 2021-08-03 18:09
pipcet[m]mps: I do have stuff working with Corellium's drivers but really the work marcan and sven and alyssa are doing is just amazing, and you should help them in any way you can :-)#asahi · 2021-08-03 13:41
pipcet[m]amw: I was confused, sorry.#asahi · 2021-08-03 13:30
pipcet[m]amw: is it possible your .config has CONFIG_CMDLINE_FORCE set?#asahi · 2021-08-03 13:27
pipcet[m]there is, but the kernel takes its command line from one of three locations (built-in, device tree, passed by boot loader) and it's a bit hard to make sure it's using the right one#asahi · 2021-08-03 07:52
pipcet[m]in the proxyclient dir?#asahi · 2021-08-03 07:51
pipcet[m]is what I use.#asahi · 2021-08-03 07:51
pipcet[m]proxyclient$ M1N1DEVICE=/dev/ttyACM0 python3.9 -m m1n1.adt --retrieve dt.bin#asahi · 2021-08-03 07:33
pipcet[m]how "dumb", though? single-channel mailbox or one channel for each endpoint?#asahi · 2021-08-03 07:11
pipcet[m](the SMC stuff to query battery status and all that stuff isn't hard, but I'm waiting for the ASC mailbox stuff to work properly)#asahi · 2021-08-03 07:10
pipcet[m]do we know it's charging properly under linux? :-)#asahi · 2021-08-03 06:45
pipcet[m]amw: pmgr_adt_clocks_enable("/arm-io/ans") ?#asahi · 2021-08-02 20:17
pipcet[m]marcan: well, yes, that's why I said A352 rather than applyProperty. I have no idea whether it even is applyProperty here, because of the firmware version dependency.#asahi · 2021-08-02 13:36
pipcet[m]alyssa: btw, I'm playing around with the DCP stuff a little, but so far all I've found out is (1) the DCP doesn't like it if you fail to initialize the shared memory area to zero before giving it access (2) the magic numbers for setting the backlight brightness are "A352", 15, and 0x20d0000#asahi · 2021-08-02 13:04
pipcet[m]very much so :-)#asahi · 2021-08-02 13:00
pipcet[m]also some of it might be set up the right way already, but relying on Apple to keep things sane seems a problematic bet at best.#asahi · 2021-08-02 12:48
pipcet[m]oh, and probably rely on m1n1 to bring up the clocks.#asahi · 2021-08-02 12:47
pipcet[m]a complete driver is fairly complex, I'd say: you need to mux the pins to the SPI interface, write a driver for the SPI chip, write a driver for the second GPIO chip so you can receive interrupts from the keyboard, and then you need to adjust applespi to handle real SPI rather than ACPI. (Just maybe you can get away with setting the pins to GPIO and bit-banging SPI over it, but that's really only good enough for boot loaders.)#asahi · 2021-08-02 10:43
pipcet[m]amw: best ask marcan about that, I don't want to do anything to ruin the PR-ability of anyone's changes :-)#asahi · 2021-08-02 10:36
pipcet[m]amw: I can answer questions about the corellium driver if that would help (and you don't want to look at it yourself)#asahi · 2021-08-01 14:12
pipcet[m]there's CONFIG_DEBUG_ATOMIC_SLEEP#asahi · 2021-08-01 11:23
pipcet[m](I think I know what it is but that seems irrelevant now :-) )#asahi · 2021-08-01 11:21
pipcet[m]sven: you can forget about the "persistent bad state" issue, by the way. Not only does your driver continue to work in that state, it actually cures it for the buggy driver, too.#asahi · 2021-08-01 09:41
pipcet[m]we're not booting the coprocessors, we're just attaching to them :-). If sven has plans to discuss this with the right people that should happen, though.#asahi · 2021-08-01 08:52
pipcet[m]the firmware-loading part seem optional and reasonably independent, to me, and the rest of the API fits very well, I think...#asahi · 2021-08-01 08:43
pipcet[m]can we combine the two approaches? use a mailbox for, uhm, the mailbox, and implement a remoteproc on top of that?#asahi · 2021-08-01 08:32
pipcet[m]alyssa: excellent, thank you very much for working on this. I'll just set myself up right here and ask you "are we done yet" every five minutes or so ;-). Have you decided whether you're going to use the mbox protocol, remoteproc/rpmsg, or roll your own yet?#asahi · 2021-07-31 21:57
pipcet[m]alyssa: thank you for that, I think it makes sense now. I can make m1n1 turn the display backlight to full brightness even when iBoot leaves it at the "very dim" setting that macOS keeps resetting it to! it's very exciting! now I just need a Linux driver so I can play with it from userland...#asahi · 2021-07-31 13:40
pipcet[m]I suspect I messed up clock initialization order, but probably not relevant, just thought I'd mention it.#asahi · 2021-07-31 13:40
pipcet[m]0x1400024f#asahi · 2021-07-31 13:39
pipcet[m]sven: ever saw a clock get stuck in 0x...4f state until you write 0xf to it again?#asahi · 2021-07-31 12:44
pipcet[m]lack of vsync is annoying, I'm not noticing the software cursor much, but my usage is hardly typical :-)#asahi · 2021-07-31 12:43
pipcet[m]marcan: it's awesome, I approve of the names and can't wait to break things with the code :-)#asahi · 2021-07-31 10:33
pipcet[m]what's the status of DCP reverse-engineering? I'm looking at the "wtf" commit of the "dcp-clusterfuck" branch, and those names totally sound like it's production-ready#asahi · 2021-07-31 08:46
pipcet[m]"The function can only be called from a process context (for now)." in the documentation for rpmsg_send, though...#asahi · 2021-07-31 08:31
pipcet[m]would that give us a standard way to handle the reserved memory regions the IOPs know about?#asahi · 2021-07-30 20:04
pipcet[m]er, wait. even weirder. on the first press I do see 01 06 01, then 01 06 01 for the release, too, then 01 06 00 for the next press, but 01 06 01 for the next release..#asahi · 2021-07-30 19:58
pipcet[m]01 fe 01 after 3 seconds, 01 00 01 after 4 seconds, then no message until it powers off#asahi · 2021-07-30 19:57
pipcet[m]03 01 00 for lid switch close, 03 00 01 for lid switch open#asahi · 2021-07-30 19:56
pipcet[m]wait, sorry, 00 for press, 01 for release#asahi · 2021-07-30 19:55
pipcet[m]by the way, on that machine I get "SMC HID Event: 01 06 01" when I push the power button, and "01 06 00" when I release it. I think you saw different codes?#asahi · 2021-07-30 19:33
pipcet[m]built a kernel off it yet? ;-)