#
…

2022-11-17

00:23psykose has quit [Remote host closed the connection]
00:24psykose has joined #asahi-dev
00:31amarioguy has joined #asahi-dev
00:33pbsds has joined #asahi-dev
01:01amarioguy has quit [Remote host closed the connection]
01:13millenialhacker has joined #asahi-dev
01:20user982492 has joined #asahi-dev
01:21millenialhacker has quit [Ping timeout: 480 seconds]
01:41amarioguy has joined #asahi-dev
01:59zalyx has quit [Quit: later alligator]
02:01zalyx has joined #asahi-dev
02:06zalyx has quit []
02:07zalyx has joined #asahi-dev
02:36millenialhacker has joined #asahi-dev
02:44millenialhacker has quit [Ping timeout: 480 seconds]
03:26chadmedhttps://github.com/chadmed/asahi-audio/tree/testing can someone with a j314 or j316 and a brave streak do me a huge favour and test these new IRs?
03:27chadmedthey sound significantly better than the previous lot to me but im really sick atm so would like a second opinion from someone who can hear properly :P
03:52Mary has quit [Quit: The Lounge - https://thelounge.chat]
03:53Mary has joined #asahi-dev
04:03trsohmers has joined #asahi-dev
04:11millenialhacker has joined #asahi-dev
04:16weitcis has quit [Remote host closed the connection]
04:16weitcis has joined #asahi-dev
04:17weitcis has quit []
04:19millenialhacker has quit [Ping timeout: 480 seconds]
04:49user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:25cylm has quit [Quit: WeeChat 3.6]
06:26weitcis has joined #asahi-dev
06:35SSJ_GZ has joined #asahi-dev
07:05millenialhacker has joined #asahi-dev
07:09jannauchadmed: have you seen my chat about profile availability in pipewire? recent pipewire before 0.3.60 required the headset mic to be present
07:19millenialhacker has quit [Ping timeout: 480 seconds]
08:25lamlam has joined #asahi-dev
08:35bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:35Dementor has quit [Remote host closed the connection]
08:36Dementor has joined #asahi-dev
08:42MajorBiscuit has joined #asahi-dev
08:43capta1nt0ad has joined #asahi-dev
08:44lamlamoh my god
08:45lamlami just did a convolution on the ane
08:45lamlam has quit [Quit: Page closed]
08:49bluetail7 has joined #asahi-dev
08:51bluetail7 is now known as bluetail
08:51Retr0id has quit [Read error: Connection reset by peer]
08:51grange_c has quit [Write error: connection closed]
08:51bluetail has quit [Read error: Connection reset by peer]
08:51pbsds has quit [Read error: Connection reset by peer]
08:51pbsds has joined #asahi-dev
08:51Retr0id has joined #asahi-dev
08:51grange_c has joined #asahi-dev
08:51riker77 has quit [Remote host closed the connection]
08:51riker77 has joined #asahi-dev
09:18millenialhacker has joined #asahi-dev
09:26millenialhacker has quit [Ping timeout: 480 seconds]
09:30marcanoh right, I had a pulseaudio patch to upstream
09:32_jannau_aoh, pulseaudio had the same problem with the headset detect?
09:46marcan_jannau_: not sure if same problem but there was a bug there
09:47chadmedjannau: is this for UCM? i figured out what we needed to change for pipewire a while ago but i cant remember what :/
09:47marcanyeah, PA UCM had a bad codepath/interaction in the hotplug case with hardware volume controls
09:48marcanI don't really care about PA in the long term but we need to carry this fix around for now at least
09:48marcan(and hopefully upstream will take the PR)
09:48weitcis has quit [Quit: Konversation terminated!]
09:49chadmediirc for pw it was some syntax thing in the speaker detection block that caused it to just give up entirely on parsing the profiles. let me see if i still have it somewhere and can test it against 0.3.60
09:50marcankettenis_: should I send the M2 MTP stuff to u-boot upstream?
09:50marcanor was there anything left to do there?
09:52_jannau_chadmed: https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1429/diffs the problem was that pipewire wanted all ports active to consider a profile active. i.e. it qworked only with headset microfone
09:52_jannau_doesn't look like it's the same issue as pa
09:53weitcis has joined #asahi-dev
09:54_jannau_does u-boot require reviewed dt-bindings for the m2 mtp?
09:56chadmedoh yeah i see, what profile do you use the device in? i dont think this matters in pro audio since i cant reproduce it
09:56chadmedall pw does is complain that theres no valid verbs for the device for some reason
09:57_jannau_marcan: did you see my m2 atcphy/usb3 tree and the dcp update to remove the currently useless 120Hz mode
09:57chadmedah yeah i see, the hotplug thing doesnt work with pro audio. that complicates things on the DSP front significantly tbh
09:58marcanah right, we should get that reviewed on Linux first
09:58marcan_jannau_: saw the m2 one, not the dcp update
10:01marcansven: I'll make the compatibles tfoo, t8103 for atcphy
10:01marcan_jannau_: which should mean we don't need the fixup for atcphy
10:01svensounds good to me
10:02bluetailchadmed may be unrelated but I fixed my pipewire not working with installing wireplumber-git from the AUR
10:03chadmedjannau: this hotplug thing fixed with 0.3.60 right? with pro audio disabled switch-on-hotplug works with no headset mic now
10:03_jannau_compatible is fine for now. I used the soc specific ones because I saw different behavior for DP on t6001
10:03_jannau_chadmed: yes
10:04chadmedyeah cool, i wonder if we can get it to work with pro audio
10:04_jannau_ony tested on devices without speakers
10:04svenDP still kinda worked with just the t8103 compatible so it's fine to have that as a fallback
10:05svenand what was different on t6000?
10:05svenI still have some hardcoded values for some registers that actually come from $somewhere
10:05chadmedit needs to work with pro audio because we cant apply DSP to the speakers otherwise. i think thats more of a DE thing though since in pro audio mode pipewire just exposes everything everywhere all at once
10:05sven(for DP, not for USB3)
10:05marcanI don't see the existing driver doing anything different for t6k
10:05marcanDP only?
10:05sveni'm pretty sure there are no differences for USB3
10:06_jannau_yes, DP only
10:06sventhe hardcoded values are DP only, yes
10:06marcanworth having the compatible just for that then, even if it's "a bit broken"
10:06svenI don't think the code for t6k is actually different, iirc it doesn't overload the dp functions
10:06marcanbut then !t8103 have to come first in the match table once you add data fields to those
10:06marcanto make sure they override it
10:07sveni'm still mostly sure it's just some if (some_magic_register & some_magic_bit) do_what_looks_like_t6k_stuff
10:07svenso it's not t6k vs t8103 but actually something that has to be done on both
10:07marcanah, yeah
10:07marcanoverride some reads and see if it affects things?
10:08svenyeah, it's still on my TODO list ;)
10:08svenif you look at the DP function you'll also see quite a few hardcoded values
10:08svenbut none of that code is triggered right now with usb3-only fwiw
10:08_jannau_sven: did you add LN_AUSPMA_RX_TOP_PMAFSM after the initial version?
10:08svenI missed that originally
10:09_jannau_ok, that was the extra thing I saw
10:09_jannau_setting LN_AUSPMA_RX_TOP_PMAFSM_PCS_OV
10:09svenit does that on t8103 as well if you switch to USB3+DP or DP-only
10:10povikwhat a mouthful
10:10svenit's already shortened from what XNU calls it
10:11svenmost of the phy regs come in pairs. you have WHATEVER and WHATEVER_OV
10:11svenyou need to set the _OV to actually override the signal
10:11leafpawz has joined #asahi-dev
10:11sven<3 LANE1_AUSPMA_RX_TOP_TJ_BLK_PMAFSM_REG4_PCS_PMAFSM_REQ
10:12leafpaw has quit [Ping timeout: 480 seconds]
10:13_jannau_the hardcoded values are not SoC specific but seems to be device specific. my mac mini used different values than sven's
10:14marcanmore fuses?
10:14svenyeah, i'll just have to figure out where it gets them from eventually. chances are it's just some of the previous MMIO reads
10:14sventhe whole driver started with literally everything hardcoded
10:14svenI just didn't get around to those values yet
10:15sventhere are also three or so writel left which just configure an entire register to some constant value
10:16svenneed to split that up into individual bits as well. just some busywork with the HV and XNU's debug log
10:19marcanjannau: merged the changes & pushed asahi-wip
10:31capta1nt0ad has quit [Remote host closed the connection]
10:31capta1nt0ad has joined #asahi-dev
10:40joske has joined #asahi-dev
10:40kov has quit [Quit: Coyote finally caught me]
10:40joskemarcan: there's a stray g in Error: arch/arm64/boot/dts/apple/t8103.dtsi:38.5-6 syntax error in latest asahi-wip
10:42marcanwhere did that come from...
10:42capta1nt0ad has quit [Quit: Konversation terminated!]
10:43capta1nt0ad has joined #asahi-dev
10:43capta1nt0ad has quit []
10:43capta1nt0ad has joined #asahi-dev
10:45joske has quit [Remote host closed the connection]
10:47marcankettenis_: confirmed that uboot works with atcphy now (tagged & package in asahi-dev)
10:52mps_ has joined #asahi-dev
10:52chadmed has quit [Quit: Konversation terminated!]
10:54mps has quit [Ping timeout: 480 seconds]
10:55digicyc has joined #asahi-dev
10:55leafpawz has quit [Remote host closed the connection]
10:56chadmed has joined #asahi-dev
11:07bisko has joined #asahi-dev
11:10svenmarcan: have you ever dumped the cd321x firmware when looking into those USB PD commands?
11:11sveni need to figure out some interrupt bits (mode discovery completed, etc.) which might be easier by just looking at the fw
11:11marcanthe external firmware is just patches/addons; I never dumped the ROM
11:11marcanI assume the ROM is also different from the standard one (that's what makes it a special partno)
11:11svenyeah, that's what I assume as well
11:11svenI saw those addons but they're more or less useless without the ROM
11:12marcanI think someone said you can dump it with SWD
11:12marcanbut that requires hardware haxx
11:12svenugh. it's a pity apple had to move around essentially all interrupt bits. the rest matches up very nicely
11:13kettenis_marcan: upstreaming MTP would be good, but it would probably be easier if we upstream the dt bindings first
11:13marcanthough I think there's an SWD mode for the sideband pins but I'm not sure if it's SWD for the chip itself or passthrough to the SoC
11:14sventhe original TPS chips also have some external flash read commands and it wouldn't surprise me if there's also hidden "read RAM" commands. but those don't exist anymore on the apple variant
11:15svenoh well, let's see what I can figure out by just poking those chips and observing the interrupt status
11:18Dcow has quit [Remote host closed the connection]
11:18Dcow has joined #asahi-dev
11:26millenialhacker has joined #asahi-dev
11:26marcansven: [ 2336.223752] WARNING: CPU: 9 PID: 608 at drivers/phy/apple/atc.c:1973 atcphy_mux_set+0x280/0x2e4 [phy_apple_atc]
11:26marcanjust got that one
11:26marcanafter a suspend/resume and reconnect
11:27marcanalso I just realized there are *4* cortex-M3s in the M1 Pro/Max DCP lol
11:27svennot surprised that happens after suspend/resume
11:27marcanLED, LTM, BLM, APT
11:27sventhat's part of a slightly fragile setup that orders dwc3 shutdown vs. mux shutdown
11:28svenit works as long as nothing unexpected like suspend/resume happens :D
11:31Major_Biscuit has joined #asahi-dev
11:32Dcow_ has joined #asahi-dev
11:34cylm has joined #asahi-dev
11:34millenialhacker has quit [Ping timeout: 480 seconds]
11:38Dcow has quit [Ping timeout: 480 seconds]
11:38MajorBiscuit has quit [Ping timeout: 480 seconds]
11:55c10l1 has quit []
11:55c10l has joined #asahi-dev
12:20marcansven: not sure if some recent change fixed suspend/resume on atcphy or it's just due to me running on the hypervisor, but it actually works now?
12:20marcanwell, it still resets devices but at least it comes back
12:23mps_ is now known as mps
12:23svenprobably atcphy being unstable as usual if you don't do certain things in just the right order
12:23svenwithout suspend/resume that's guaranteed
12:23svenwithout suspend/resume you can probably hit some edge cases it doesn't like
12:25svenusually as long as first dwc3 shuts down and then atcphy and as long as first atcphy is configured again and only then dwc3 starts everything should work
12:32svenI need to rework the way that order is ensured for altmode anyway and I'll see how to enforce it with suspend as well
12:32svenI don't really know without looking at the code how exactly the resume part is triggered
12:33svenbut I guess what might happen is dwc3 shutdown -> pipehandler to dummy -> resume -> pipehandler to usb3 -> dwc3 init and it may not like that without a atcphy reinit inbetween
12:35svenplus maybe tipd also triggers something? dunno
12:36svenat least whatever happens doesn't break it without a reboot. getting *that* correct was truly annoying
12:36marcansven: okay yeah it works only sometimes
12:36marcanI get the [ 33.679950] phy-apple-atc b03000000.phy: pipehandler lock not acked, this type-c port is probably dead until the next reboot.
12:36svenyeah, as expected
12:36svenyup, that message is a bit older when that was still true :D
12:37svenprobably makes sense to change it to something like "you'll probably have to replug the connector to make it work"
12:50marcanok, fixed the dcp suspend/resume issue (solution: actually use the DRM suspend/resume helpers which work properly, instead of open-coding something broken :p)
12:52jannauI wasn't aware that there was an issue but I haven't tested dcp suspend/resume much
12:53marcanyou get a black screen on j314/j316 at least, until a DPMS cycle
12:54marcan(wouldn't be surprised if wayland works)
12:54marcan(because it actually triggers swaps)
12:54marcanthere was also a ton of warning spew from locked DARTs
12:55sveni would be disappointed that wouldn't be happening on -edge!
12:55marcanI think that's the worst of the suspend/resume issues since sometimes there's no good way to get back the screen
12:55millenialhacker has joined #asahi-dev
12:55svenlike, where's the fun if nothing breaks in something called bleeding edge :D
12:56marcanwould be nice if we can fix the atcphy ordering too, but that can wait until after release
12:56marcanwhich at this point is going to be next week
12:56marcan(could do it on the weekend, but let's optimize for the media cycle shall we...)
12:57sveni probably won't get around to fixing suspend/resume but you can probably hack it by issuing tps_disconnect in the tipd suspend handler and tps_connect in the resume handler
12:57jannauI should see to wire up the pointer plane then X11 would do swaps on pointer movement (that's for after the release)
12:57sventhat tipd thing is doing a lot of the heavy lifting for us :D
12:58marcanwell, I don't think you're *supposed* to actually trigger a connect/disconnect, I think devices are supposed to survive a suspend/resume to some extent? though right now dwc3 dies anyway so I'm guessing that's the first thing to fix there
12:58svendwc3 definitely shuts down on suspend
12:58sveni'm re-using that code to also shut it down when switching to USB_ROLE_NONE
12:58marcanyeah and doesn't come back on resume clean
12:58marcan[ 27.649409] xhci-hcd xhci-hcd.0.auto: xHC error in resume, USBSTS 0x401, Reinit
12:59marcanwhich causes a full re-enumerate
12:59marcan(this has always been like that on usb2; it does not happen on the PCI controllers)
12:59svenmaybe I misremember but I think dwc3 actually removes the xhci device on suspend
12:59marcanon macos?
12:59jannaunext dcp TODO item is m2 support which might be a single digit of line changes in dcp and more dart changes
13:00sven if (!PMSG_IS_AUTO(msg) && !device_may_wakeup(dwc->dev)) {
13:00sven dwc3_core_exit(dwc);
13:00svenah.. so that's what linux does on suspend
13:00marcanummmm does that kill the whole thing?
13:00svendwc3_core_exit does that, yes
13:00marcanoh god why is this driver/hardware so broken
13:00svencore_exit also asserts the hard reset line
13:01sven<sven> i probably won't get around to fixing suspend/resume but you can probably hack it by issuing tps_disconnect in the tipd suspend handler and tps_connect in the resume handler
13:02svenmaybe just setting device_may_wakeup and/or PMSG_IS_AUTO just skips that
13:02svenwho knows
13:02svencore_exit also calls into atcphy to shut down
13:03svenso if you manage to skip dwc3_core_exit we might be good
13:03millenialhacker has quit [Ping timeout: 480 seconds]
13:13millenialhacker has joined #asahi-dev
13:22millenialhacker has quit [Ping timeout: 480 seconds]
13:22marcansven: I think that whole codepath is bullshit. you are not supposed to go off resetting host controllers during suspend.
13:23marcanxHCI already has a defined protocol for going into suspend, and you can certainly put the parent device into low-power mode but definitely not do a full reset
13:23svenI'm willing to bet that is done to work around a quirk on some random hardware
13:23marcanit's supposed to continue to track connect/disconnect events during suspend so the kernel can know whether a device was removed to decide how to re-enumerate it
13:24marcanthere is a hack in the kernel to work around the current situation, but it has to be manually enabled and has lovely failure cases like "if you suspend, remove a USB drive, insert an identical one, and resume, and it doesn't have a serial number, your filesystem will explode"
13:24marcan(because it can't know it's a different drive)
13:24svenjust look for some of the recent dwc3 threads in linux-usb
13:24sventhere's e.g. some intel platform that breaks if they probe extcon at the wrong time (lol)
13:25sventhere are also two separate ways it orders xhci_init and phy_set_mode
13:25sveni'd expect set_mode followed by xhci init
13:25marcanalso you can't identify reconnects via tipd since they could happen purely on the USB side (e.g. if you're using a type A adapter cable)
13:25marcanso you *have* to keep dwc3 working to at least detect hub events
13:25svenbut that also breaks some intel platform
13:26svenit really would not surprise me if that "reset everything on suspend" is to workaround more crap like that
13:28sveni'd try to just always make that if with !device_may_wakeup(dwc->dev) false in the suspend and resume functions
13:28svenif that block is skipped it also won't call into atcphy so it should just survive as well
13:30svenah, wait, it'll hit the DWC3_GCTL_PRTCAP_OTG path anyway
13:31svenreplace if (PMSG_IS_AUTO(msg)) with if(true) and it might just survive
13:31sven(after case DWC3_GCTL_PRTCAP_OTG:)
14:03as400 has quit [Remote host closed the connection]
14:08maximbaz has quit [Quit: bye]
14:10maximbaz has joined #asahi-dev
14:10Cyrinux has quit []
14:12Cyrinux has joined #asahi-dev
14:20marcansven: ok so there are several problems here. nuking those codepaths *and* keeping the power domains up avoids the dwc3 error, but the devices still disconnect.
14:20marcanso that's probably a phy or tipd issue?
14:20marcanto dwc3 it just looks like a disconnect/connect
14:20svenhrm, probably
14:20svenso dwc3 survives?
14:21marcanif I keep the PDs up and comment out those dumb reset codepaths, yes
14:21marcanhowever, macOS *does* power down the dwc3 power domains on sleep. Haven't tested what they do for USBMS (the only real problem case where you can't afford to do blind reconnects)
14:21marcanso there must be a way to do that with recovery, while maintaining port state
14:21svenhrm, tipd shouldn't issue any mux_set so atcphy should survive as well I think
14:22svenunless tipd calls that tps6598x_disconnect it'll leave atcphy alone
14:22svenand if dwc3 survives it'll also leave atcphy alone
14:25marcanmaybe it's the phy rpm
14:25marcanlet me drop that too
14:26marcanah but atcphy doesn't even do rpm
14:26svenmaybe also try trace_atc.py and see what happens on suspend
14:28millenialhacker has joined #asahi-dev
14:28marcansven: nothing
14:28svenyeah, that's what I expected. dunno why dwc3 sees a disconnect then :/
14:35marcansven: it could be this is just broken in dwc3
14:36marcanI mean the xHCI core does the standard xHCI sleep stuff including save state and such
14:36marcanI guess we need to figure out what macOS does
14:36sventrue. given how broken hotplug is on these machines anyway that also wouldn't surprise me
14:36marcan(could be it just works around it with the moral equivalent of that hack I mentioned earlier)
14:36marcanbut for that we need to make the hypervisor survive suspend/resume cycles which ugh
14:36sventhat doesn't sound like fun
14:40kazuki_ has quit [Quit: Konversation terminated!]
14:43millenialhacker has quit [Ping timeout: 480 seconds]
14:51marcansven: so from what I see tracing the xHCI registers, it puts the port into suspend state properly, but then on the way out it just refuses to come out of suspend and it eventually resets it
15:00svenmaybe the resume needs some additional phy interaction?
15:00sveni guess we really need to take a look at what macos does to do this properly :/
15:02alyssasven: good morning
15:03alyssa*reads backlog*
15:03alyssa...nope!
15:03alyssa has quit [Quit: leaving]
15:13xcpy0 has quit [Remote host closed the connection]
15:14marcansven: I think I give up on this for now
15:15marcanI'm going to do another merge/tag/build with the dcp suspend fixes
15:16svenyeah, it doesn’t really break anything. people who use -edge may just have to reconnect usb devices once it comes out of suspend
15:17marcanwell, it's not great if you have USB mass storage devices
15:17marcanor anything actually running like USB sound cards or capture cards
15:17marcan*cough* my streaming setup *cough*
15:18marcanbut then again, once I do switch (when lina gets OBS running properly...) the machines are quiet enough I don't need to suspend it
15:19svensure, but it’s called -edge for a reason :p
15:20sveni wouldn’t want to ship this to users who expect this to work
15:20mpsthis is new tag asahi-6.1-rc5-11?
15:20* mpswants to test
15:21svenbut bleeding edge with a disclaimer what happens to usb on suspend sounds fine with me tbh
15:35mpsnice, screen 'comes back' after resume now, on m1pro macbook
15:36maria has quit [Ping timeout: 480 seconds]
15:37millenialhacker has joined #asahi-dev
15:51millenialhacker has quit [Ping timeout: 480 seconds]
16:19c10l has quit [Quit: Bye o/]
16:25c10l has joined #asahi-dev
16:30cylm has quit [Quit: WeeChat 3.6]
16:37marcanyes, I just fixed that
16:37marcanit's on asahi-dev
16:44digicyc2 has joined #asahi-dev
16:46digicyc has quit [Ping timeout: 480 seconds]
16:58millenialhacker has joined #asahi-dev
17:02leafpaw has joined #asahi-dev
17:03digicyc2 has quit [Ping timeout: 480 seconds]
17:06maria has joined #asahi-dev
17:06millenialhacker has quit [Ping timeout: 480 seconds]
17:08leafpaw has quit [Remote host closed the connection]
17:09leafpaw has joined #asahi-dev
17:19leafpawz has joined #asahi-dev
17:21leafpaw has quit [Ping timeout: 480 seconds]
17:32amarioguy2 has joined #asahi-dev
17:34Major_Biscuit has quit [Ping timeout: 480 seconds]
17:36millenialhacker has joined #asahi-dev
17:44amarioguy2 has quit [Ping timeout: 480 seconds]
17:45millenialhacker has quit [Ping timeout: 480 seconds]
17:56nicolas17 has joined #asahi-dev
18:30svenugh… guess I’m back to rebooting the soc when trying to bring cio up *sigh*
18:35* jannauimagines how annoying that would be without *vdmtool
18:36svennah, cio is nice enough to do the reboot for me
18:36svenapparently because I messed up and brought down atcphy while acio was still running
18:36svenit really doesn’t like that
18:37svenit probably even saves me a second or so compared to running vdmtool this way :D
18:53amarioguy2 has joined #asahi-dev
18:58trsohmers has quit [Ping timeout: 480 seconds]
18:58trsohmers has joined #asahi-dev
20:27xcpy0 has joined #asahi-dev
20:28amarioguy2 has quit [Ping timeout: 480 seconds]
20:29amarioguy2 has joined #asahi-dev
20:31Axenntio has joined #asahi-dev
20:37millenialhacker has joined #asahi-dev
20:37Axenntio has quit [Read error: Connection reset by peer]
20:44as400 has joined #asahi-dev
20:45millenialhacker has quit [Ping timeout: 480 seconds]
20:53jluthra has quit [Remote host closed the connection]
20:53jluthra has joined #asahi-dev
21:20nicolas17 has quit [Ping timeout: 480 seconds]
21:34jannaulooks like atcphy might broke interfacing with m1n1. I'm getting https://paste.debian.net/1261051/ on boot of a device with m1n1 in proxymode
21:38sventhat warn_on essentially means dwc3 did now shut down
21:40svenwas this a disconnect when dwc3 was in device mode?
21:41svens/now/not/
21:47jannaunot sure, the both systems were long connected (both running linux) and I noticed the repeated error only after several disconnects/reboots of the m1n1 system
21:48amarioguy2 has quit [Ping timeout: 480 seconds]
21:50svenuh, so this was in the host machine?
21:52millenialhacker has joined #asahi-dev
21:56sventhat’s weird. that shouldn’t be any different than disconnecting any other device
21:56svenanything before that warn?
21:56svenusually it should be xhci shutting down
22:05jannaujust xhci shutting down. dmesg from between two warning https://paste.debian.net/1261053/
22:06jannauport recovers when a other usb device is connected
22:07sventhats looks like it’s doing what it’s supposed to do
22:07millenialhacker has quit [Ping timeout: 480 seconds]
22:09svenso for some reason phy_power_off isn’t called
22:33robherhow does one get the kernel log early? 'earlycon=efi' doesn't seem to work or I'm dying before earlycon is up.
22:35jannaurobher: earlycon=ttySAC0
22:36robherjannau: no serial port on MBP 14 though?
22:38jannauwhen you boot via m1n1, m1n1 virtualises the primary uart and provides it via usb cdc
22:39jannauthe usb-c port closest to the magsafe connector can route the reaul primary uart but needs special hardware/software
22:49robherjannau: humm, I guess I need a USB C to A cable. asahi-wip (6.1-rc1 based) from about a month ago boots but USB is deferred (presumably a new dependency in the DT missing the driver). The current asahi-wip with edge config does not.
22:57jannaurobher: current asahi-wip gained a type-c phy driver, dwc3 in the current devicetree references that but 6.1-rc1 misses the driver
22:58millenialhacker has joined #asahi-dev
23:06millenialhacker has quit [Ping timeout: 480 seconds]
23:26robherjannau: Right. Without the edge config, now it is booting for me.
23:33SSJ_GZ has quit [Ping timeout: 480 seconds]
23:35Cyrinux has quit []
23:36Cyrinux has joined #asahi-dev
23:46weitcis has quit [Ping timeout: 480 seconds]
23:58weitcis has joined #asahi-dev
…