#
…

2023-09-29

01:08tbodt_ has joined #asahi-dev
01:37tbodt_ has quit [Ping timeout: 480 seconds]
01:46nepeat has quit [Quit: ZNC - https://znc.in]
01:50nepeat has joined #asahi-dev
02:00gabuscus has quit []
02:03Wormn has joined #asahi-dev
02:12Wormn has quit [Quit: Konversation terminated!]
02:13Wormn has joined #asahi-dev
02:18Wormn has quit [Quit: Konversation terminated!]
02:18Wormn has joined #asahi-dev
02:22jeisom has quit [Ping timeout: 480 seconds]
02:35gabuscus has joined #asahi-dev
02:38crabbedhaloablut has joined #asahi-dev
02:42loki_val has joined #asahi-dev
02:42crabbedhaloablut has quit [Read error: Connection reset by peer]
03:01skipwich has quit [Quit: DISCONNECT]
03:02skipwich has joined #asahi-dev
03:12Wormn has quit [Remote host closed the connection]
03:17cylm has joined #asahi-dev
03:51TellowKrinkle has quit [Remote host closed the connection]
03:52TellowKrinkle has joined #asahi-dev
03:56tristan2_ has joined #asahi-dev
03:58tristan2 has quit [Ping timeout: 480 seconds]
04:05midou has joined #asahi-dev
05:06dcow has joined #asahi-dev
05:14dcow has quit [Ping timeout: 480 seconds]
05:39gladiac has joined #asahi-dev
05:44wille-io has quit [Quit: Ping timeout (120 seconds)]
05:59wille-io has joined #asahi-dev
06:38lena6 has joined #asahi-dev
07:04lena6 has quit [Ping timeout: 480 seconds]
07:24jonmastershi folks, I would like to take a look at the wip thunderbolt support - is there a good branch to be looking at?
07:25jonmasters(this is NOT for an eGPU, this is to try some simple PCIe devices for fun in an enclosure)
07:43i509vcb has quit [Quit: Connection closed for inactivity]
07:58systwi has joined #asahi-dev
08:02gladiac has quit [Quit: k thx bye]
08:02systwi_ has quit [Ping timeout: 480 seconds]
08:12systwi_ has joined #asahi-dev
08:16systwi has quit [Ping timeout: 480 seconds]
08:50AnuthaDev has joined #asahi-dev
08:51slp has joined #asahi-dev
09:06jonmastersI found the USB4 DART patches from March but I assume I also need corresponding updated DTBs for those...anyone got a pointer to where I can find the bits? I assume I'll need to patch an m1n1 too
09:16jannegjonmasters: see atcphy-20230219, nothing else is public since public WIP branches unfortunately result in user support per private emails
09:17jannegcanonical source of the DTBs is the kernel tree which are appended to m1n1 as payload and are filled with information on the system
09:19janneghotplug in that branch is not reliable, you might need to connect/disconnect a few times
09:20jannegnecessary thunderbolt device tree changes might be only hooked up for the m1 mac mini
09:22jannegI've seen some weird PCIe issues with that branch. a samsung evo 980 nvme did not work at all, an intel 2.5GB nic in a HP usb4 hub did not deliver IRQs
09:27jannegjonmasters: ah, I see, you're already in contact with sven on mastodon
09:27svenhah, I was just going to suggest he could talk to you :)
09:28svenmy brain doesn’t fully work yet so feel free to take over :)
09:28jannegsure, go back to relax and recover
10:03dcow has joined #asahi-dev
10:11dcow has quit [Ping timeout: 480 seconds]
10:23dcow has joined #asahi-dev
10:29pounce has quit [Remote host closed the connection]
10:29pounce has joined #asahi-dev
10:54linaeiln, janneg: Pushed a bunch of fixes and refactoring to my branch again, but I didn't get around to looking at t8112... I think there are still weird races and things like that around startup/shutdown.
10:55espo has joined #asahi-dev
10:55hightower2 has joined #asahi-dev
10:55linaI'm running gstreamer in a random kill loop now to see if I can find any weird races. So far one thing I am seeing is DART translation faults after shutdown, and also I think the suspend thing doesn't work in some cleanup paths?
10:55linaBasically error/early abort handling needs work I think
10:55linaThis is what I'm running now: while true; do timeout -k 1 -s 9 $((1+RANDOM%3)).$(printf %03d $((RANDOM%1000))) gst-launch-1.0 v4l2src ! 'video/x-raw,width=720,height=1280' ! videoconvert ! fakesink; done
10:56linaI also fixed vertical video in ffmpeg ^^ (sent them the patch)
10:56janneglina: I'll rebase my t8112 branch but probably won't do anything else
10:57dcow has quit [Ping timeout: 480 seconds]
10:57jannegI'll test t6001 with 13.5 as well, need do new install for that
11:03leiofwiw, if you want your gstreamer pipeline to exit more cleanly for this after a random amount of time/frames, v4l2src has num-buffers property to which you could give a random number of frames to let through as well and then end-of-stream and exit
11:03linaThe point is actually letting it exit uncleanly ^^
11:04linaI want to hit the weird error handling corner cases, not just clean exit
11:06leiowas too eager to try to help, as gst is an area I at least know :)
11:06dcow has joined #asahi-dev
11:07jeisom has joined #asahi-dev
11:11lena6 has joined #asahi-dev
11:14dcow has quit [Ping timeout: 480 seconds]
11:17lena6 has quit [Read error: Connection reset by peer]
11:36hightower2 has quit [Ping timeout: 480 seconds]
11:39hightower2 has joined #asahi-dev
11:40dcow has joined #asahi-dev
11:48dcow has quit [Remote host closed the connection]
11:48dcow has joined #asahi-dev
11:57hightower2 has quit [Read error: Connection reset by peer]
12:02espo has quit [Quit: WeeChat 4.0.5]
12:06espo has joined #asahi-dev
12:07hightower2 has joined #asahi-dev
12:09wontons has joined #asahi-dev
12:10wontons has quit []
12:15jeisom has quit [Quit: Leaving]
12:28jeisom has joined #asahi-dev
12:37linaeiln: I'm running into a rare pmgr issue where the main isp_sys domain refuses to power on with bit 0x800 set, and setting bit 0x1000 fixes/resets it. I'll try to figure out what that means... I think it's one of the ones you used?
12:44hightower2 has quit [Read error: Connection reset by peer]
12:48hightower2 has joined #asahi-dev
12:48hightower2 has quit [Remote host closed the connection]
12:49hightower2 has joined #asahi-dev
12:56amarioguy2 has quit [Remote host closed the connection]
12:57amarioguy has joined #asahi-dev
13:37linaPushed some pmgr-related stuff, hope it improves the Âcorner cases...
13:51hightower2 has quit [Read error: Connection reset by peer]
13:52hightower2 has joined #asahi-dev
13:58qyliss has quit [Remote host closed the connection]
13:59qyliss has joined #asahi-dev
14:01i509vcb has joined #asahi-dev
14:06jeisom has quit [Ping timeout: 480 seconds]
14:09jeisom has joined #asahi-dev
15:01slp has quit [Ping timeout: 480 seconds]
15:02linaThe recovery stuff I tried to add doesn't work... it gets the PS going, but then random CPUs get wedged immediately after that ;;
15:11linaI think there is something weird that happens when you kill -9 the app using the camera. Shutdown fails, but I see the same VB2 callbacks getting called...
15:13linaAaaaa we're using wait_event_interruptible_timeout() for commands ;;
15:13linaSo on signals all that breaks...
15:20hightower2 has quit [Read error: Connection reset by peer]
15:21linaOK, looks much cleaner now ^^
15:26jacksonchen666 has joined #asahi-dev
15:30linaI'm going to leave it all night starting/killing captures while looping some ffmpeg compiles, if nothing goes horribly wrong I think we're good ^^
15:34linaActually removed it now anyway, in a fixup
15:34linaI should sleep ^^
15:58jacksonchen666 has quit [Ping timeout: 480 seconds]
16:05lawrence has quit [Ping timeout: 480 seconds]
16:05lawrence has joined #asahi-dev
16:07xcpy0 has quit [Read error: Connection reset by peer]
16:07xcpy0 has joined #asahi-dev
16:08stipa is now known as Guest1676
16:08Guest1676 has quit [Read error: Connection reset by peer]
16:08stipa has joined #asahi-dev
16:11arekmx has joined #asahi-dev
16:11arekm has quit [Read error: Connection reset by peer]
16:13slp has joined #asahi-dev
16:13wille-io has quit [Read error: Connection reset by peer]
16:13wille-io has joined #asahi-dev
16:14_dhewg has joined #asahi-dev
16:14dhewg has quit [Read error: Connection reset by peer]
16:15_dhewg is now known as dhewg
16:15jonmastershey thanks janneg and sven
16:16jonmastersI'll take a look at that branch. The right workflow is to take a dtb and rebuild m1n1 right? there's a flow to chainload an m1n1...is that what you usually do to test, or do you replace the original m1n1?
16:18hightower2 has joined #asahi-dev
16:19hightower3 has joined #asahi-dev
16:19hightower2 has quit [Read error: Connection reset by peer]
16:19j`eyjonmasters: replacing stage1 m1n1 means going via recoveryOS, so you want to just replace stage2
16:21jonmastersso just the uboot payload?
16:21marcanI/most of us just load kernels/devicetrees over USB
16:21jonmastersis that what patches the dtbs in this stack?
16:21jonmastersI've seen that page before - will take a look
16:21marcanlook for the backdoor proxy mode section to enable USB loading (with a timeout so it defaults to normal boot), no need to replace anything
16:21jonmastersmarcan: when the dtbs are patched, that's the stage2/uboot doing it?
16:22marcanthat's my workflow these days, install normally, enable that (can even be done during the install step2 part, in a new terminal tab)
16:22marcanyes, stage2 handles runtime dtb changes
16:22marcanstage1's only job is to load stage2
16:22tenkuu has joined #asahi-dev
16:22marcanI've been moving more minor init stuff from stage1 to stage2 since it's safer/more flexible that way over time, in principle stage1 should do the minimum possible to load stage2 or enable USB mode
16:23jonmastersok, I'll use another M1 with the USB load method - probably weekend at this point
16:23marcanwith the backdoor mode stage1 breaks into USB mode and then you can just chainload m1n1 (for updates) and linux.py a kernel, or use the hypervisor, or whatever
16:23marcanthe other machine can be any arbitrary computer fwiw
16:23j`eyjonmasters: it doesnt need to be another M1
16:24jonmastersI'm seeing a possible relaxed memory issue with a certain driver on another Arm platform and wanted to see if it showed up with the most relaxed of them all - reason I am tinkering with thunderbolt :)
16:25jonmastersalso, I'm totally blown away with the progress here, it's outrageous
16:25jonmastersI will never underestimate you ever again ;)
16:26marcanjonmasters: FWIW page isn't fully up to date, but you always want to chainload a new m1n1 before hypervisor or linux.py to make sure you use your up to date tree, not whatever stage1 is
16:27marcanmy usual recipe for testing kernels bare metal is (in m1n1/proxyclient): make -C .. && python tools/chainload.py -r ../build/m1n1.bin && tools/linux.py <...>/arch/arm64/boot/Image.gz <...>/arch/arm64/boot/dts/apple/t8112-j413.dtb <...>/initramfs.cpio.gz -b 'debug rootwait root=/dev/nvme0n1p6 rootflags=subvol=root'
16:27maz has quit [Ping timeout: 480 seconds]
16:28marcanfor hypervisor: make -C .. && tools/run_guest_kernel.sh <path to linux build tree root> 'debug rootwait root=/dev/nvme0n1p6 rootflags=subvol=root' <...>/initramfs.cpio.gz
16:28marcan(tools/run_guest_kernel.sh will do the chainload itself)
16:28maz has joined #asahi-dev
16:30jonmastersI've been reading through your wiki a bit and do plan to dive into the m1n1 from first principles when I've got some time, it's a great project for learning AS innards
16:30jonmastersbut for now, chainload and playing this weekend
16:30marcanyeah, it's a nice toolset to hack on pretty much all the hardware :)
16:32marcanthe backdoor proxy mode will break boot when any of the two TTY devices are opened, so when I'm using it I just have a tools/picocom-sec.sh running in another terminal which will trigger the proxy, and also become the hypervisor vUART if you use that
16:32marcan(see udev/80-m1n1.rules for the rules to set up the /dev nodes properly)
16:32jonmastersand any generic Linux box can be the other end, ok
16:33marcanit's just USB
16:33jonmastersso just a USB-C->C cable and a dell XPS ok
16:33marcanlow level serial stuff and remote hard reboots are possible with another Mac or custom hardware, but not at all required
16:33jonmastersgreat, that's my desk down in my lab already :)
16:33jonmastersI'm seeing maz in a couple weeks and he's bringing one of his toys for me
16:34marcan(if you use the hypervisor you can always ^C and `reboot` as long as it doesn't get into a really bad wedge state)
16:34jonmastersI haven't picked up an M2 mini yet (NV2)
16:34jonmastersbut I will etc.
16:34jannegany computer with an aarch64 (cross-)compiler
16:35jonmastersthat's great
16:35marcanI've heard rumors that some Apple people use m1n1 with a macOS host because it's better than their own tooling ;)
16:39jonmastersI've heard similar
16:40espojanneg: sry forgot to tell you earlier, tried the bluetooth fixes and it works perfectly ( even for none logitech products ). I have a custom build keyboard which also went to a connect yes/no loop before. Applied your patch and now it connect just fine.
16:40marcancool, I'll merge the bluetooth stuff (and a bunch of kernel backlog I have) soon
16:41rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
16:41Guest1620 has quit [Quit: Bridge terminating on SIGTERM]
16:41espoi can also try a logitech keyboard ( let me search for it should be laying somewhere ) then i can also test it with an actual logitech product
16:42espoyep working as well paired an logitech mx keys.
16:44Jamie has joined #asahi-dev
16:45Jamie is now known as Guest1682
16:45rhysmdnz has joined #asahi-dev
16:55jacksonchen666 has joined #asahi-dev
17:00jacksonchen666 has quit []
17:15hightower3 has quit [Read error: Connection reset by peer]
17:27espo has quit [Quit: WeeChat 4.0.5]
17:28espo has joined #asahi-dev
17:47flom84 has joined #asahi-dev
17:50Cyrinux9474 has quit []
17:52Cyrinux9474 has joined #asahi-dev
17:52janneglina: t8112 / fw 13.5 works after rebase onto isp/t602x-v2
17:52jannegand adapting to the pmgr changes
17:55hightower2 has joined #asahi-dev
18:05jannegsometimes. still seing crashes. recovery after crashes works but if it doesn't crash again might result in broken colors, cyan/magenta tinted
19:11tenkuu has quit [Read error: Connection reset by peer]
19:20jeisom has quit [Ping timeout: 480 seconds]
19:25tenkuu has joined #asahi-dev
19:36tenkuu has quit [Read error: Connection reset by peer]
19:49tenkuu has joined #asahi-dev
19:52tenkuu has quit [Read error: Connection reset by peer]
20:06tenkuu has joined #asahi-dev
20:13maximbaz has quit [Quit: bye]
20:13maximbaz has joined #asahi-dev
20:24kidplayer_666 has joined #asahi-dev
20:26AnuthaDev has quit [Remote host closed the connection]
20:26AnuthaDev has joined #asahi-dev
20:27AnuthaDev has joined #asahi-dev
20:31kidplayer_666 has quit []
20:31kidplayer_666 has joined #asahi-dev
20:34AnuthaDev has quit [Quit: AnuthaDev]
20:37kidplayer_666_ has joined #asahi-dev
20:38kidplayer_666_ has quit [Remote host closed the connection]
20:40nela has quit [Quit: bye!]
20:40nela has joined #asahi-dev
20:41kidplayer_666_ has joined #asahi-dev
20:42kidplayer_666 has quit [Ping timeout: 480 seconds]
20:42kidplayer_666_ has quit [Read error: Connection reset by peer]
20:55kidplayer_666_ has joined #asahi-dev
21:00kidplayer_666_ has quit [Remote host closed the connection]
21:01kidplayer_666_ has joined #asahi-dev
21:08kidplayer_666_ has quit [Remote host closed the connection]
21:08kidplayer_666_ has joined #asahi-dev
21:08lena6 has joined #asahi-dev
21:20kidplayer_666_ has quit [Read error: Connection reset by peer]
21:20kidplayer_666_ has joined #asahi-dev
21:22kidplayer_666_ has quit [Remote host closed the connection]
21:23kidplayer_666_ has joined #asahi-dev
21:24kidplayer_666_ has quit [Read error: Connection reset by peer]
21:49flom84 has quit [Ping timeout: 480 seconds]
22:02cylm has quit [Ping timeout: 480 seconds]
22:27jeisom has joined #asahi-dev
22:47i509vcb has quit [Quit: Connection closed for inactivity]
22:59loki_val has quit []
23:17eiln has joined #asahi-dev
23:22eilnlina: thanks for the fixes, studying them
23:22eilnI am wary of indexing "bt_surf" by strings though. "MISC" is everything they couldn't be bothered to name, and I'm surprised 0xc000 is a filter. maybe we can narrow it down by tracking state? also we shouldn't need to vmap every surface now
23:23eilnjanneg: cyan/magenta tinted? uh oh. that doesn't sound like the grey/grainy + rainbow spec err I used to get, mine was a filter graph ordering err
23:26eiln has quit [Quit: WeeChat 4.0.4]
23:28jannegeiln: looked like an exposure filter, mostly cyan with brighter spots in magenta
23:29jannegI suspect the crashes are power-domain related
23:31jannegpushed to isp/t8112
23:32jeisom has quit [Ping timeout: 480 seconds]
…