15:06 <emxll> Hey, was wondering if there are any known processes to get any info at all out of a failing boot? I'm trying to make m1n1 work on my t6030 (m3 pro) but so far I've not been able to debug anything (proxy mode doesn't work). I've been trying to get any indication that my boot code is running (write red squares to framebuffer, hardfault, etc) but nothing has shown an effect.

15:10 <emxll> Could it be that I have to put the m1n1 build in my Container as well or is running kmutil configure-boot (without copying m1n1 to my boot container) enough?

15:15 <sven> configure boot is enough

15:16 <sven> do you have a hardware serial connection? (e.g. another mac or central scrutinizer?)

15:16 <emxll> Unfortunately i dont

15:16 <sven> bringup is going to be very challenging then :/

15:17 <emxll> unfortunate, I guess I might wait then

15:17 <emxll> honestly I'd be happy getting 1 bit out of it

15:18 <sven> there are some pull requests related to m3 support that haven’t been merged yet afaik

15:18 <emxll> I'll take a look

20:22 <Lyude> btw - is this the most active dev channel for asahi stuff? I ask because I'm wondering if I can run questions by y'all that I have surrounding Asahi's DRM tree bindings, since I'm currently working on expanding those to include modesetting bindings

20:23 <krbtgt> there's #asahi-gpu too

20:23 <krbtgt> i think the drm/kms people check more frequently there

21:22 <kidplayer666> Lyude,: there's also the matrix channel

21:33 <sven> that’s mostly fedora development though and also bridged to irc