#
✕ nick:pipcet[m]
#asahi · 2021-04-24 12:16
pipcet[m]there's documentation for a very similar TI chip, but you probably know that :-)
#asahi · 2021-04-24 12:16
pipcet[m]yay!
#asahi · 2021-04-24 12:16
pipcet[m]Linux or m1n1?
#asahi · 2021-04-24 12:14
pipcet[m] * so I can use the other port in gadget mode for about the first minute, and then it stays in whatever connection state it had then.
#asahi · 2021-04-24 12:14
pipcet[m]so I can use the port in gadget mode for about the first minute, and then it stays in whatever connection state it had then.
#asahi · 2021-04-24 12:13
pipcet[m]except the shared irqs mean the second chip's interrupt handler busy-loops until Linux decides it's had enough.
#asahi · 2021-04-24 12:12
pipcet[m]it works if I don't bring it up :-)
#asahi · 2021-04-24 12:12
pipcet[m]oh. sorry :-)
#asahi · 2021-04-24 12:09
pipcet[m]sven: do you happen to know whether unplugging the charger and reinserting it works if you're still in m1n1?
#asahi · 2021-04-24 11:32
pipcet[m](no idea how free you are to do that, there's probably a horrible table of interdependencies somewhere)
#asahi · 2021-04-24 11:32
pipcet[m]I think you assign each pin to an interrupt group
#asahi · 2021-04-24 11:25
pipcet[m]the proposed bindings look good to me (though not very different from the Corellium ones), but I think we should use ADT names for the "clocks"/power gates
#asahi · 2021-04-24 11:23
pipcet[m]sorry, I meant you need GPIO for the keyboard, not for the typec chips
#asahi · 2021-04-24 11:22
pipcet[m]I don't think we need to be overly polite about that part, it's impressive work but does need (at least) cleanup and (quite possibly) rewriting the way you guys appear to be setting out to do
#asahi · 2021-04-24 11:21
pipcet[m]"some"
#asahi · 2021-04-24 11:21
pipcet[m]I'm pretty sure there's an actual controller, they use SPI a lot
#asahi · 2021-04-24 11:20
pipcet[m]sven: the i2c one? it's rather annoying because the two ports share an interrupt line so if you try booting without SMP support, the corellium code deadlocks because chip0 is receiving interrupts from chip1 but chip1 hasn't registered its isr yet.
#asahi · 2021-04-24 11:19
pipcet[m]yes, you need another GPIO pin to enable the device, and the SPI bus is mapped to GPIO pins as well.
#asahi · 2021-04-24 11:19
pipcet[m](I still think we should support booting Linux directly from a minimally-intrusive macho)
#asahi · 2021-04-24 11:18
pipcet[m]no keyboard support in u-boot? :-)
#asahi · 2021-04-24 11:17
pipcet[m]for example, that's how the keyboard works
#asahi · 2021-04-24 11:17
pipcet[m]interrupts are often routed through the GPIO controller, yes.
#asahi · 2021-04-23 23:11
pipcet[m]what's the magic trick for associating a backlight blanking control to the frame buffer?
#asahi · 2021-04-23 21:19
pipcet[m]they're cheap enough, but AM would still be a waste
#asahi · 2021-04-23 21:15
pipcet[m]when I saw the amfm node I was wondering whether they'd put in a radio broadcast receiver as well :-)
#asahi · 2021-04-23 21:11
pipcet[m]so maybe it's more like PCI hotplugging than the existing rfkill code.
#asahi · 2021-04-23 21:10
pipcet[m]I was under the impression the gP0d pin was more than rfkill: I think it cuts power to the entire module.
#asahi · 2021-04-21 22:06
pipcet[m]hmm, so it's not absolutely trivial to boot a macho kernel, it seems, but that doesn't mean much.
#asahi · 2021-04-21 21:20
pipcet[m]if there really is a macho binary that starts macos we should get that working ASAP and see what we can make it do
#asahi · 2021-04-21 21:18
pipcet[m]I might do that.
#asahi · 2021-04-21 21:15
pipcet[m]not the third one, hopefully :-)
#asahi · 2021-04-21 21:15
pipcet[m]easier to do, higher likelihood of working, less valuable data.
#asahi · 2021-04-21 21:13
pipcet[m]if it's that easy, I still think it might be worth it to try stealing a CPU core from macos and run our code on that in parallel to macos. We wouldn't see the MMIO accesses directly, but we could do some debugging nonetheless
#asahi · 2021-04-21 21:11
pipcet[m]that would be wonderful!
#asahi · 2021-04-21 21:10
pipcet[m]done this = prevented virtualization of their hardware
#asahi · 2021-04-21 21:10
pipcet[m]I can think of relatively cheap ways for Apple to potentially have done this, so all I'm saying it might be a good idea to work out how to start MacOS in EL0 first, then worry about the mmiotracer if there's a chance it might work.
#asahi · 2021-04-21 21:06
pipcet[m]and do we know that testing whether it's running under a hypervisor and bailing if there is one isn't the first thing that does?
#asahi · 2021-04-21 21:03
pipcet[m]so, uh, where is the xnu kernel, actually?
#asahi · 2021-04-21 21:01
pipcet[m]I very briefly tried to even find whatever macos boots instead of our macho binary
#asahi · 2021-04-21 21:00
pipcet[m]can we actually boot macos yet?
#asahi · 2021-04-21 20:59
pipcet[m]what are the mmiotracer plans, actually? play hypervisor for MacOS using m1n1?
#asahi · 2021-04-21 20:56
pipcet[m]well, if it helps us get better code I'm perfectly okay with some drama :-)
#asahi · 2021-04-21 13:13
pipcet[m]I don't consider the wifi bit in particular a major issue, but it might be a good place to start if people here insist on rewriting all the Corellium code since it's relatively self-contained.
#asahi · 2021-04-21 13:12
pipcet[m]thanks, I'll have a look
#asahi · 2021-04-21 13:10
pipcet[m]or am I misreading that?
#asahi · 2021-04-21 13:09
pipcet[m]it's not a simple memory-mapped device, I think that's limited to those cases?
#asahi · 2021-04-21 13:09
pipcet[m]syscon?
#asahi · 2021-04-21 13:07
pipcet[m]probably, the firmware's a little trickier though, IIUC
#asahi · 2021-04-21 12:14
pipcet[m]I just wanted to point out there's a userspace hack as well. /usr/bin/wifistart in their ubuntu image or something like that.
#asahi · 2021-04-21 12:07
pipcet[m]they have some horrible scheme to load the driver, figure out which firmware to use, then re-load the driver after setting the firmware path

plus ›