2021-06-05
01:20Emantor has quit [Quit: ZNC - http://znc.in]
01:20Emantor has joined #asahi
01:37modwizcode has joined #asahi
02:16phiologe has joined #asahi
02:18yuyichao has quit [Quit: Connection closed for inactivity]
02:19PhilippvK has quit [Ping timeout: 480 seconds]
03:05marvin24_ has joined #asahi
03:09marvin24 has quit [Ping timeout: 480 seconds]
03:10aquijoule_ has joined #asahi
03:16richbridger has quit [Ping timeout: 480 seconds]
03:56Namidairo has quit [Quit: ZNC - https://znc.in]
03:56Namidairo has joined #asahi
04:03marvin24 has joined #asahi
04:06marvin24_ has quit [Ping timeout: 480 seconds]
04:28modwizcode has quit [Remote host closed the connection]
05:16amwMy shell.py connection is failing with Bad command on connection, possibly due to unable to find ADT node pci-bridge1.pcie? - see https://paste.debian.net/1200069
05:17amwI am thinking of re-installing the m1n1 on the M1 macbook, but perhaps something else needs to be updated
05:19Emantor[m]bloom: Barebox, https://www.barebox.org was initially an U-Boot fork which removed a lot of unsupported code and adheres closer to the Linux driver interfaces, making driver ports to/from the kernel much easier. It also provides a somewhat saner CLI than U-Boot, at least to my eyes.
05:21Emantoramw: do you have any error messages in the dmesg of the computer your mac is connected too? On my desktop mainboard at least one of the USB ports did not reliably work with m1n1 and I also needed a stable kernel update.
05:23VinDuv has joined #asahi
05:24amwEmantor: No error messages - seems to be fine - here's the only messages https://paste.debian.net/1200071
05:29Emantoramw: m1n1 is the latest build? Are you chainloading latest m1n1 beforehand? S_BADCMD looks to be raised if m1n1 doesn't know the command that the python-proxy requests.
05:33amwok - I'm running the latest on the client / python side, but a 1-2 week old one M1 side. I'll try the chainload first
05:36amwYes that's fixed it - python3.9 proxyclient/chainload.py build/m1n1.macho - I can now run shell.py!
06:00adamcstephens has quit [Quit: The Lounge - https://thelounge.chat]
06:04adamcstephens has joined #asahi
06:13pipcet[m]Emantor: barebox looks really cool, thanks for sharing the link. What did you have to change?
06:16EmantorNothing much, I hacked in DBEUG_LL support, but adjusted the S3C Uart driver now, so it works as well. It's really not much code, I'll see if I can get USBGadget up and running, than I can simply chainload from m1n1.
06:24pipcet[m]Emantor: I meant the configuration as well (I only just heard about barebox). If you want to share that, that would be great :-)
06:25jannauamw: sound like a regression of making checksums optional. I'm not sure if we care as long as chainloading a newer m1n1 works
06:25amwjannau: Yep - I added a note to the Developer Quick Start to help any others in the future. I'm fine with that
06:26alessandrorzz[m]Hi, someone can help me with an issue in arch Linux?
06:26Emantorpipcet[m]: Do you have a 1.2V Uart on the debug port? Otherwise barebox isn't really usable on m1 yet.
06:28Emantorjannau: I think m1n1 on his computer was missing the get/set_SIMD command, so the proxy complained, I don't think this has to do with the checksums.
06:29amwI do have a vague memory that I may have run it with the checksums so I suspect Emantor is right.
06:31pipcet[m]Emantor: no, but just getting it to chain-load would be nice. I understand it doesn't have the drivers yet.
06:36VinDuvwhen it starts up, shell.py fetches methods out of the ProxyUtils instance so you can directly use msr() in the shell instead of u.msr(), but the way it does that makes it fetch the SIMD properties defined here (https://github.com/AsahiLinux/m1n1/blob/main/proxyclient/proxyutils.py#L241)
08:12gladiac has quit [Read error: Connection reset by peer]
08:13gladiac has joined #asahi
08:25VinDuvamw: You can try https://github.com/AsahiLinux/m1n1/pull/69 , it should allow you to get a shell without chainloading m1n1 first
09:22jannauworks but is quite noisy and slow. should be handled in m1n1 with the ability to ignore uninteresting event types and numbers
09:28sveni can hack the reconnect to work already. just need to check read32(0x502a90008) & 0x0100000 and then do set32(0x502a90004, 3); clear32(0x502a90004, 3)
09:36amwVinDuv: Sorry not sure how to handle that pull-request - I have only git clone of the repository here
09:40VinDuvamw: you can download and apply the patch manually https://github.com/AsahiLinux/m1n1/commit/b135733d733d12907aa0d5af87c770380ae8dc9f.diff -- it’s just a couple of lines in proxyclient/shell.py
09:44pugguu has joined #asahi
09:51jannausven: much better with filtering in m1n1: https://gist.github.com/jannau/8a1e86d6a3178bc328b3f25ca1a96a68
10:00pugguu has quit [Read error: Connection reset by peer]
10:00pugguu has joined #asahi
10:01pugguu has quit [Read error: Connection reset by peer]
10:02pugguu has joined #asahi
10:03Izumoo has quit [Ping timeout: 480 seconds]
10:20pugguu has quit [Read error: Connection reset by peer]
10:20pugguu has joined #asahi
10:20pugguu has quit [Read error: Connection reset by peer]
10:20pugguu has joined #asahi
10:24choozy has joined #asahi
10:31jannauI'm not sure if the disconnects are exact, there might be regular USB traffic after I marked the position but before I disconnect
10:32svennotice how it just goes off to write to the phy regs after you connect again? it's probably some other interrupt
10:40jannauI'm off till later. https://gist.github.com/jannau/eaa1baa11ae615cc74293912d5c6c71c is the patch I use for usb-c/aic tracing
10:40pugguu has quit [Remote host closed the connection]
10:42pugguu has joined #asahi
11:06choozy has quit [Ping timeout: 480 seconds]
11:51TheLink has quit [Quit: ZNC 1.8.2 - https://znc.in]
11:51TheLink has joined #asahi
12:02bgb_ has joined #asahi
12:04GreatGodvin[m] has joined #asahi
12:17TheLink has quit [Quit: ZNC 1.8.2 - https://znc.in]
12:17TheLink has joined #asahi
12:22bgb_ has quit [Ping timeout: 480 seconds]
12:22aquijoule_ has quit [Ping timeout: 480 seconds]
12:29richbridger has joined #asahi
12:45malvo has joined #asahi
12:48bgb_ has joined #asahi
12:56bgb_ has quit [Ping timeout: 480 seconds]
13:20bgb_ has joined #asahi
13:50tsida has quit [Remote host closed the connection]
13:53GreatGodvin[m] is now known as ohdamn[m]
13:57VinDuv has quit [Quit: Leaving.]
14:02bgb_ has quit [Ping timeout: 480 seconds]
14:06bgb_ has joined #asahi
14:14bgb_ has quit [Ping timeout: 480 seconds]
14:27VinDuv has joined #asahi
14:37bgb_ has joined #asahi
14:51bgb_ has quit [Ping timeout: 480 seconds]
15:13bgb_ has joined #asahi
15:21bgb_ has quit [Ping timeout: 480 seconds]
15:35Shiz has quit [Read error: Connection reset by peer]
15:36Shiz has joined #asahi
15:45bgb_ has joined #asahi
15:53bgb_ has quit [Ping timeout: 480 seconds]
15:53pugguu has quit [Read error: Connection reset by peer]
15:54pugguu has joined #asahi
15:58pugguu has quit [Read error: Connection reset by peer]
15:58pugguu has joined #asahi
16:07pugguu has quit [Read error: Connection reset by peer]
16:07pugguu has joined #asahi
16:17bgb_ has joined #asahi
16:25bgb_ has quit [Ping timeout: 480 seconds]
16:48bgb_ has joined #asahi
16:57bgb_ has quit [Ping timeout: 480 seconds]
17:00bps has joined #asahi
17:07pugguu has quit [Read error: Connection reset by peer]
17:07pugguu has joined #asahi
17:19pugguu has quit [Read error: Connection reset by peer]
17:20pugguu has joined #asahi
17:23bgb_ has joined #asahi
17:31bgb_ has quit [Ping timeout: 480 seconds]
17:35tsida has joined #asahi
17:45jannauany idea why some adt nodes have "#interrupt-cells = 2"? interrupt property looks like it is consectutive interrupts
17:48hexchain has joined #asahi
17:54pugguu has quit [Read error: Connection reset by peer]
17:55pugguu has joined #asahi
17:59jnthe #*-cells properties usually specify how many cells should be used when the node in question is used as a resource provider for something else, i.e. when the GPIO controller is used to provide GPIO interrupts
18:00pipcet[m]so GPIO has seven AIC interrupts, multi-touch has a single GPIO interrupt described by two cells, the first of which is a pin number and the second presumably encoding whether it's edge triggered/level triggered/low/high, or something.
18:01bps has quit [Ping timeout: 480 seconds]
18:24pugguu has quit [Read error: Connection reset by peer]
18:24pugguu has joined #asahi
18:50jannausven: I haven't found an obvious interrupt which fires at connect/disconnect. 190 from "/arm-io/gpio" is very noisy so I can't if that one is used
18:53jannauI suspect the interrupts property for nodes which uses /arm-io/gpio as interrupt specifies gpio pin, index into /arm-io/gpio's interrupts to get the mapped AIC interrupt
18:55sventhe other alternative i can think of would be to specify if the interrupt triggers on hi/low edge/level
18:55malvo has quit [Ping timeout: 480 seconds]
19:05bps has joined #asahi
19:07pugguu has quit [Ping timeout: 480 seconds]
19:25jannauhave you seen a pa semi manual? mac os uses 0x18, 0x2c and 0x44 in addition to the registers in the linux driver
19:41Emantor0x44 is weird, always set 1 during the write and reset directly afterwards. From my i2c traces 0x08 with mask 0xff00 could indicate number of received bytes.
19:41pipcet[m]uhm, they are named and documented in the corellium driver (but if you prefer guessing, that's okay, of course)
19:42malvo has joined #asahi
19:43svensure, i believe marcan also has a pa semi datasheet he got by asking the guy who wrote the linux driver. but either way, to sniff i2c traffic all you should need are the two fifo registers
19:47malvo has quit [Remote host closed the connection]
19:48malvo has joined #asahi
19:48malvo has quit [Remote host closed the connection]
19:48malvo has joined #asahi
19:51jannausecond interrupt cell is more likely flags, the second cell of the bluetooth node is 0x20_0002
20:01kubes has joined #asahi
20:02kubes has quit []
20:02kubes has joined #asahi
20:05kubes has quit []
20:14Emantorsven: I took a look at your dma question in #armlinux, and just saw now that it's been there for a while. I am off now, I can look at this some more tomorrow.
20:45bps has quit [Ping timeout: 480 seconds]
20:52VinDuv has quit [Quit: Leaving.]
21:05bps has joined #asahi
22:15bps has quit [Ping timeout: 480 seconds]
22:17sveni always hit "panic(cpu 0 caller 0xfffffe0014c6f0f8): "ApplePMGR: virtual void ApplePMGR::initDriver(IOService *):1557 REQUIRE failed: id != kIDReserved"
22:20brentr123[m]I have a spare linux machine
22:20brentr123[m]my pc has a dualboot
22:21brentr123[m]ah but its x86
22:21brentr123[m]may not work
22:21brentr123[m]so what command should i do on the linux machine to help you?
22:22brentr123[m]I have like 5
22:22brentr123[m]1 mac
22:22brentr123[m]2 pcs
23:11apetresc has quit [Quit: ZNC 1.8.2 - https://znc.in]
23:19bloom^ Is this something people have seen loop (along with dumped registers) when trying to boot hv?
23:22bloomnow i see a progress bar come up and lots of MMIO spammed at me but the display has gone black so I don't know if it's making progress
23:23sveni've only seen "panic(cpu 0 caller 0xfffffe0014c6f0f8): "ApplePMGR: virtual void ApplePMGR::initDriver(IOService *):1557 REQUIRE failed: id != kIDReserved" no matter what i do :(
23:26choozy has joined #asahi
23:27choozy has quit []
23:35apetresc has joined #asahi