#
…

2022-11-23

00:01amarioguy2 has joined #asahi-dev
00:04millenialhacker has quit [Ping timeout: 480 seconds]
00:27zshrc has joined #asahi-dev
00:29zshrc has quit []
00:29jmalexan has joined #asahi-dev
00:31jmalexan is now known as NotDisliked
00:36weitcis_ has quit [Ping timeout: 480 seconds]
00:37weitcis_ has joined #asahi-dev
00:48user982492 has joined #asahi-dev
00:55amarioguy2 has quit [Ping timeout: 480 seconds]
00:55amarioguy2 has joined #asahi-dev
00:56amarioguy2re: the "go into OS selector every time" question there's probably some hacky workaround but officially sanctioned i don't think so
01:03cyrozappovik: Thanks again for your help--I've managed to successfully download and extract the ASMedia firmware. Interestingly, the firmware version ("191118_70_11_11") is newer than any other I've seen in the wild so far. I wonder if they fixed the bug where trying to read from two devices simultaneously can sometimes cause a bad DMA write...
01:05amarioguy2 has quit [Ping timeout: 480 seconds]
01:07weitcis_ has quit [Quit: Konversation terminated!]
01:15millenialhacker has joined #asahi-dev
01:23millenialhacker has quit [Ping timeout: 480 seconds]
01:25stsmwg has joined #asahi-dev
01:26stsmwg has quit []
01:28stsmwg has joined #asahi-dev
01:32NotDisliked has quit [Quit: Konversation terminated!]
01:50cyrozapI have some questions regarding the DART IOMMU. If my understanding is correct, some Apple SoCs only have a 36-bit address space, while others have a 42-bit address space. Is this just the physical limit, and the I/O virtual address can be larger (e.g., greater than 48 bits)? Or does this limit apply to the virtual addresses as well? Like, would Linux running on an Apple SoC ever tell a PCIe device to
01:50cyrozapwrite to an address larger than 48 bits?
01:56stsmwg has quit [Quit: Lost terminal]
02:24chadmedmarcan: i think 7cf5c453e960 on asahi-installer collides with the latest asahi-scripts
02:25chadmedpython tries to install /usr/bin/asahi-fwextract now which makes no sense if we have it in asahi-scripts
02:40marcanah, yeah
02:43marcancyrozap: we're still having trouble with the "reset to ROM code for firmware upload" step sometimes, so if you find anything wrong in the code please do tell...
02:43marcanI just reverse engineered that by copying what macOS does, I don't know what the indirect write regs do
02:52marcanalso now I wonder where the hell I got ASM2214 from, that has to be a typo...
02:52millenialhacker has joined #asahi-dev
02:52marcanprobably meant to write 2142
02:52marcanlovely that I typoed the firmware filename... good thing we have fwextract to fix that...
02:54mac456 has joined #asahi-dev
03:00cyrozapmarcan: "2214" comes from the RCFG/FW headers, which are "2214A_RCFG"/"2214A_FW" for the ASM2142 and ASM3142 (https://github.com/cyrozap/asmedia-xhc-re/blob/59708d5b5eb17593f6f5459f2bf20b73e90b159d/monitor/make_image.py#L32). I assume "2214A" is ASMedia's internal name for the chip, but I have no idea why they rotate the number right by one place compared to the model numbers they write on the chips.
03:00millenialhacker has quit [Ping timeout: 480 seconds]
03:00marcanohh that's where I got that from
03:01cyrozapI have a Kaitai Struct definition for their firmware images, in case you're curious: https://github.com/cyrozap/asmedia-xhc-re/blob/59708d5b5eb17593f6f5459f2bf20b73e90b159d/tools/asm_fw.ksy
03:02marcanstill should probably use the public part number for the firmware name
03:04marcancyrozap: re the instability, maybe we need the confirmed mmio write thing?
03:05marcanor just the sleeps
03:05cyrozapIf you do use the public part number, I'd use 2142 instead of 3142, since as far as I can tell the 3142 is just a newer die revision of the 2142. No idea what the _actual_ differences are, but they both use the same firmware images and have identical mask ROMs.
03:05cyrozapAnd yes, you might need to confirm the writes.
03:06marcanI think some people said they are the same chip, and the firmware is the only difference
03:06marcanas in you can turn a 2142 into a 3142
03:06marcan(IIRC 3142 has higher speed USB support?)
03:06marcancould be a product differentiation thing
03:15mac456 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:18cyrozapAccording to the product pages (https://web.archive.org/web/20181003174332/http://www.asmedia.com.tw/eng/e_show_products.php?cate_index=175&item=178 and https://web.archive.org/web/20181003174337/http://www.asmedia.com.tw/eng/e_show_products.php?cate_index=175&item=179), compared to the 2142, the 3142 supports "Multiple INs"--I don't know enough about USB to understand what that means. Other than that,
03:18cyrozapthey support the same speeds on both USB and PCIe. Since ASMedia no longer lists the 2142 on their website, and the 2142 and 3142 have different chip version numbers (which you can access by doing an indirect read to byte 0x150B2), I'm pretty sure they just fixed something in the silicon and called it a new chip to avoid having to explain multiple 2142 revisions to their customers. I hope to eventually
03:19cyrozaphave someone decap and image both the 2142 and the 3142 so we can confirm if they really are the same die, and check the mask revision numbers to confirm what changed.
03:25user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:28beeblebrox has quit [Quit: Konversation terminated!]
03:29nicolas17 has quit [Quit: sleep]
03:41cyrozapmarcan: Regarding instability, thinking again about what I needed to do to get direct firmware loading working on the older chips, I think you might need to confirm the writes to the address registers for both the indirect code RAM writes and the indirect MMIO writes. And yes, you might also need the sleeps, too. My Python code using PCI config space accesses is slow enough that I didn't experience
03:42cyrozapmuch issues (though I do remember adding the sleeps for the indirect MMIO writes), but C kernel code writing to PCI MMIO may simply be writing all the registers too fast for the chips internal busses to keep up.
03:43cyrozapAnd to be clear, those sleep values were obtained by experimentation and I just set them to "good enough to work reliably but not too slow", so you might want to experiment to see if you can get away with smaller delays.
03:46cyrozapOh, and one more thing:
03:57cyrozapActually, never mind.
03:58cyrozapI wrote a bunch of stuff, but then realized it didn't apply :P
04:03cyrozapI think I'm going to try some stuff myself on an ASM3142 I have here, and report back with my findings.
04:10cyrozapThis write (https://github.com/AsahiLinux/linux/blob/602fee88eb0603f4d7576797397aff6b33b41765/drivers/usb/host/xhci-pci-asmedia.c#L233-L234) halts the CPU (I think by holding it in reset), so anything the code ROM does is just going to get thrown away when that write happens. And when it comes out of reset executing from code RAM, the loaded firmware will do the same init stuff (clearing/initializing
04:10cyrozapMMIO registers) that the code ROM would have done, so having the code ROM do that too is redundant.
04:27mac456 has joined #asahi-dev
04:33weitcis has joined #asahi-dev
04:38weitcis has quit [Quit: Konversation terminated!]
04:48pthariensflame has joined #asahi-dev
04:54pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
05:45mac456 has quit [Ping timeout: 480 seconds]
05:49millenialhacker has joined #asahi-dev
06:01millenialhacker has quit [Ping timeout: 480 seconds]
06:13tmlind has quit [Quit: leaving]
06:14tmlind has joined #asahi-dev
06:14nickchan has joined #asahi-dev
06:14nickchan has left #asahi-dev [#asahi-dev]
06:21Graypup_ has quit [Quit: meow]
06:21Graypup_ has joined #asahi-dev
06:29lethalnyan has quit [Quit: kill -9 -1]
06:29lethalbit has joined #asahi-dev
06:38nickchan has joined #asahi-dev
06:38nickchan has left #asahi-dev [#asahi-dev]
06:44fossdd has joined #asahi-dev
06:49SSJ_GZ has joined #asahi-dev
07:03dsharshakov has joined #asahi-dev
07:04chadmed has quit [Quit: Konversation terminated!]
07:04chadmed has joined #asahi-dev
07:05dsharshakovchadmed: could you please discuss new audio requirements in PipeWire IRC room? Not urgent
07:05millenialhacker has joined #asahi-dev
07:06chadmedthere are none at the moment actually, i figured out how to integrate the compressor in a sane way
07:07dsharshakov has quit [Remote host closed the connection]
07:07chadmedactually we might want the equal loudness plugin to work properly at some point
07:09dsharshakov has joined #asahi-dev
07:11dsharshakovSo you managed to make woofers not touch the lower case?
07:11chadmedyeah that problem is all fixed, the final frontier now is just tying the volume control to a port on a plugin in the chain
07:12chadmedi.e. linking the volume control to the volume knob on the equal loudness plugin
07:12dsharshakovOkay, so my task is limited to loading filter chain for now?
07:13chadmedyep, safety et al will be handled elsewhere either in the DSP chain or as an external thing that talks directly to alsa
07:13millenialhacker has quit [Ping timeout: 480 seconds]
07:13chadmedso all we need out of wireplumber is hiding the "real" device and loading the filter chain automatically a la UCM
07:16dsharshakovSure, disclaimer WP isn't a safety software!!!
07:16dsharshakovWhats up on safety research btw? Will it live in kernel or a daemon monitored by it?
07:20chadmedsupposedly a userspace daemon monitoring the V/ISENSEs of the speaker amps that will talk directly to alsa and cut the volumes in alsamixer dynamically to prevent meltdown
07:20chadmedso we dont need to worry about it from a DSP perspective, the compressor is there because the cones flapping against the chassis is not a meltdown problem, its a physical constraint problem
07:21chadmedand simply lowering the max volume to fix it is stupid because you lose a boatload of headroom and make the whole thing quieter when really you just want certain frequencies quieter for tiny fractions of a second at a time
07:21dsharshakovThat simple? No need to handle VI sense in PW to avoid approaching limits using DSP?
07:21chadmednope, which im ambivalent about
07:22chadmedon one hand implementing that in pipewire is probably going to be nightmarish since it has to keep track of _all_ the mixer controls and stuff and then that would need to be generalised for all similar devices with some new system/format for safety rules
07:22chadmedbut at the same time that really does sound like good long term goal...
07:23dsharshakovYup. And why not a kernel based alarm system for emergency shutdown?
07:24chadmedwe already have that, the amps cut out on certain failure conditions and theyve been programmed to bring themselves back up after doing so
07:24dsharshakovOh btw wanted to ask povik to add a panic handler turning safety mute on just in case. At least on PC systems hang can keep the audio playing
07:24chadmedthe other thing is having safety stuff outside of any particular audio server means itll work for everyone using bare alsa, pulse, etc
07:25dsharshakovYes, but why not a simple averaging thing for vi in kernel?
07:25chadmedsomething something floating point i think idk
07:26dsharshakov has quit [Remote host closed the connection]
07:26chadmedalso why bother with a semi-hacky kernel gaffer tape solution when we _know_ what we need to do to implement it properly and can do so with much more freedom in userspace?
07:27dsharshakov has joined #asahi-dev
07:28dsharshakovWell, simpler and feels safer than a daemon monitored by a watchdog
07:28chadmedyeah but simpler is not better in this case
07:28eiln has joined #asahi-dev
07:28chadmedwhats important to prevent meltdown is the temperature of the coils and magnets, and to derive that from V/I we need a bunch of floating point maths
07:28chadmedthe actual V/I by themselves arent useful
07:28dsharshakovWell, less things that could break, bug out or be mishandled by users
07:29dsharshakovWell, fpu stuff is hard for kernel, yea
07:30chadmedsure and thats why the kernel driver already handles _obviously_ wrong stuff, like clamping down the amp gains so that you cant drive enough current through them to _instantly_ pwn them
07:31dsharshakovHow is watchdogging planned to be done?
07:31chadmedwith the derived coil temperature we can just determine when theyre getting too hot and taper down the mixer controls until they cool down again
07:32dsharshakovI cannot imagine a proper solution to monitor the speakersafety daemon to be sure it's doing well and we're safe to use the amps
07:32chadmedit only needs to be tested once, all the values for the temperature model come from apple so its not like we're flying blind
07:32dsharshakovMath principles of the thing are pretty clear to me
07:32chadmedwe know the formula, we know the coefficients we need to plug into it, we know it works in macos
07:33chadmedwe just need to implement it, verify once that it actually does turn the mixer controls down when its meant to, then we can just leave it alone
07:33dsharshakovBut what if it hangs or get killed by megabrain users?
07:33dsharshakovKernel driver is less prone to that
07:34chadmedyeah, it would be nice to just emergency kill output if the daemon is not running
07:35Graypup_ has quit [Quit: meow]
07:35turo has quit [Remote host closed the connection]
07:35svenbecause you generally want to avoid floating point in the kernel. you can also just make the watchdog ping it and if it hasn’t seen any feedback in aome time just kill the output
07:35Graypup_ has joined #asahi-dev
07:35millenialhacker has joined #asahi-dev
07:35turo has joined #asahi-dev
07:35dsharshakovWhat would be the api for watchdog? Where would watchdog be?
07:36chadmedbut ^, we just cannot implement this modelling in the kernel and you cannot rely on V/I alone even as an estimation because impedance/resistance change with temperature which is what we are trying to measure
07:37dsharshakovI understand it's not to be in kernel. But userspace monitoring should be very robust and resilient against failures
07:37chadmedi think at some point we just need to say "look, we have taken every reasonable precaution but if you run 'killall do-not-kill-this' then youre beyond saving sorry"
07:38dsharshakov* or users messing with it as well
07:38dsharshakovWhat if it get OOM killed?
07:38svenI don’t think anyone proposed an api yet and it doesn’t make much sense to discuss it before that
07:38chadmedyeah but we cant help users messing with it, to paraphrase qui gon jinn, theres always a stupider user
07:39dsharshakovNeed better protection against fails
07:39svenand again, just make it ping the kernel and the kernel shutdown on timeout
07:40chadmedlets get the stuff we're actively working on ready to ship before we start worrying about this in too much detail anyway
07:41dsharshakovpovik: my idea for enhanced speaker safety is to also have a panic handler disabling TAS2764 in case of kernel panic. I think admac will keep sending a stuck audio fragment in case cpu hangs
07:41chadmedas far as a standard asahi install goes now that we have pipewire we can make things "safe enough" OOB for brave users to try out
07:42dsharshakovYep, will work on that! Need to port things to new wp 0.5 and fix validity issues
07:42chadmedwith the DSP chain in place and the latest kernel driver im confident enough to say its impossible to break the speaker array. what we need extra stuff for is to _guarantee_ that safety to _everyone_
07:53dottedmagThis is not what is in the latest blog update, isn't it? «Of course, you could limit the volume to a known-safe level, but this would result in significantly reducing the overall volume and leave a lot of unused headroom for most normal music and audio signals!»
07:53millenialhacker has quit [Ping timeout: 480 seconds]
07:53dsharshakov has quit [Remote host closed the connection]
07:54chadmedthats exactly what im saying though
07:54chadmedwe cant just brute force a lower volume in the kernel because then you lose headroom and things sound bad at low volume etc
07:54chadmedso we need to do two things
07:55chadmeda) be able to dynamically control the volume based on how hot the driver is
07:55chadmedb) dynamically control the volume based on the strength of the input to stop the cones "bottoming out" on the chassis
07:55chadmedb) is easy and we do this in DSP already, a) is harder and is what we're talking about
07:56chadmedbeing able to do that dynamically means that we get to keep all the headroom available when its safe to do so and only start capping stuff when we need to
07:57Graypup_ has quit [Ping timeout: 480 seconds]
07:57dottedmagI still don't get it. Is it something like "unless we have a heartbeat, volume is capped to overall-safe level, but as long as the monitoring daemon is live, the volume can go beyond the statically-safe limit, based on output from that daemon"?
07:57dsharshakov has joined #asahi-dev
07:57turo has quit [Ping timeout: 480 seconds]
07:57tpw_rules has quit [Ping timeout: 480 seconds]
07:58chadmedwell again we havent gotten that far but thats one way to do it
07:59chadmedthe point dsharshakov is making is that the kernel driver should do something _like_ that if the daemon isnt running to stop the speakers from melting if the daemon crashes or is killed
07:59dottedmagyeah, the driver should fail-safe, obviously.
07:59dsharshakovYes, that is the proper approach when all the safety mechanisms are in place to make sure every single moment amps work there's strict observation to keep things safe. When no daemon is present, set low hardware volume caps unless it appears and starts monitoring.
07:59dsharshakovAlso ensure robust panic and hang handling
08:00Graypup_ has joined #asahi-dev
08:00dsharshakovAnd after daemon shakes hands no one can take over hw gain control while it's running. Even root
08:01turo has joined #asahi-dev
08:01chadmedcan you make alsa lock how kcontrols from userspace?
08:01chadmeds/how/out
08:01dsharshakovOfc not a protection from malware running as root, but a measure against messing with sudo alsactl
08:02millenialhacker has joined #asahi-dev
08:04tpw_rules has joined #asahi-dev
08:05tobhe has joined #asahi-dev
08:08dsharshakov has quit [Remote host closed the connection]
08:10tobhe_ has quit [Ping timeout: 480 seconds]
08:10millenialhacker has quit [Ping timeout: 480 seconds]
08:12eilngithub is still giving me hell
08:13eilnoh sorry -- forgot to re-introduce myself. my nickname before was "lamlam", i.e. ane guy. my real name is eileen (handles use eiln).
08:14eilnin the mean time ive enabled 1D element-wise mode! add/mult/min/max working good
08:15eilnstill fighting some float packing and tiling for multi-dim...
08:20SSJ_GZ has quit [Remote host closed the connection]
08:20SSJ_GZ has joined #asahi-dev
08:21millenialhacker has joined #asahi-dev
08:24tobhe_ has joined #asahi-dev
08:27Graypup_ has quit [Ping timeout: 480 seconds]
08:27turo has quit [Ping timeout: 480 seconds]
08:29tpw_rules has quit [Ping timeout: 480 seconds]
08:29turo has joined #asahi-dev
08:29tobhe has quit [Ping timeout: 480 seconds]
08:29millenialhacker has quit [Ping timeout: 480 seconds]
08:29Graypup_ has joined #asahi-dev
08:30tpw_rules has joined #asahi-dev
08:35ChaosPrincesseiln: are you using a weird email address on ghithub
08:36ChaosPrincessas in - a weird domain
08:37eilnno i have gmail and proton
08:38eilnargh the support page updated with " Due to high support volume.." and are asking "up to seven business days" ..
08:39eilnAPI is slowly breaking too.. can't search code, etc.
08:46TellowKrinkleI've been randomly getting 100-200kbps clones recently
08:46TellowKrinkle I thought it was just my internet being funny but maybe not
08:46capta1nt0ad has quit [Read error: Connection reset by peer]
08:46dsharshakov has joined #asahi-dev
08:46dsharshakovIt might be right time to have redundant mirrors of essential repository on g.fd.o
08:48dsharshakovBut that won't help organizing tons of bits branches however
08:49dsharshakoveiln: what're your plans on UAPI to expose ANE to apps? How suitable does accel from 6.2 feel?
08:51dsharshakov has quit [Remote host closed the connection]
08:53eilndsharshakov: great question, no idea. im not even sure where it would even fit under drivers/, if i get to that point
08:53dsharshakov has joined #asahi-dev
08:54eilni dont know apple terminology too well but im pretty sure accel is their cpu framework.
08:54dsharshakovThat would depend on memory model
08:54dsharshakovAccel subsystem of Linux kernel I mean, read news about 6.2
08:55chadmedaccel seems like a good fit from preliminary reading
08:55chadmedi guess itll take a little while for userspace applications to start making use of it though
08:55svenplease stop skipping to step 100 when step 1 isn't even done :D
08:56dsharshakov has quit [Remote host closed the connection]
08:57eilnagree, exciting stuff but i still havent figured out dma interleave when size >= 32
08:58svenlina's gpu UAPI also started with essentially a hack and now she's only slowly converging towards something upstreamable
09:01dsharshakov has joined #asahi-dev
09:02dsharshakovchadmed: if it could be wired up to TensorFlow PluggableDevice API, then tf apps will be able to make use of ANE even in case supported op count is low. Unified memory gives us possibilities to not care about moving data between ANE and CPU being slower than benefits from initial ops implementation
09:03dsharshakov has quit [Remote host closed the connection]
09:03sven<sven> please stop skipping to step 100 when step 1 isn't even done :D
09:09zimsneexh has joined #asahi-dev
09:10millenialhacker has joined #asahi-dev
09:10dsharshakov has joined #asahi-dev
09:11mazmarcan: solved my X issue with 6.1 on m2: the FB_EFI was getting in the way. with 6.0, simpledrm is able to take over from EFI, but not with 6.1, apparently. just disabled the option, and all is good.
09:11dsharshakovAlright, sorry for that. Sometimes having an outline of end product can help developing core as well, so I added those ideas to keep them around
09:11dsharshakov has quit [Remote host closed the connection]
09:18millenialhacker has quit [Ping timeout: 480 seconds]
09:19eilnconsidered doing literally 1+2 a feat yesterday, longg way to go
09:19eiln has quit [Quit: Page closed]
09:26svenyeah, these things go a bit different when reverse engineering hardware. it makes sense to start these discussion once it comes to implementing a linux driver but before that it's just guesswork because it's unclear what the hardware can even do
09:27svenand running something equivalent to "1+2" is already a big step when reverse engineering :)
09:38bluetail9 has joined #asahi-dev
09:39MajorBiscuit has joined #asahi-dev
09:40a_plastic_bag has joined #asahi-dev
09:43leitao has joined #asahi-dev
09:46bluetail has quit [Ping timeout: 480 seconds]
09:46bluetail9 is now known as bluetail
09:46a_plastic_bag has quit [Quit: WeeChat 3.7.1]
09:54leitao has quit [Ping timeout: 480 seconds]
10:23millenialhacker has joined #asahi-dev
10:30zimsneexh has quit [Quit: zimsneexh]
10:31millenialhacker has quit [Ping timeout: 480 seconds]
10:37Kasper has joined #asahi-dev
10:46Kasper has quit [Remote host closed the connection]
10:57CatDentures has joined #asahi-dev
12:11jvzr has joined #asahi-dev
12:18jvzr has quit [Remote host closed the connection]
12:25millenialhacker has joined #asahi-dev
12:31cylm has joined #asahi-dev
12:33millenialhacker has quit [Ping timeout: 480 seconds]
12:39weitcis has joined #asahi-dev
12:45pjakobsson has joined #asahi-dev
12:46weitcis has quit [Remote host closed the connection]
13:39jvzr has joined #asahi-dev
13:42millenialhacker has joined #asahi-dev
13:50millenialhacker has quit [Ping timeout: 480 seconds]
13:57Heyb4r has joined #asahi-dev
13:58millenialhacker has joined #asahi-dev
14:06millenialhacker has quit [Ping timeout: 480 seconds]
14:22Heyb4r has quit [Remote host closed the connection]
14:22Heyb4r has joined #asahi-dev
14:24MajorBiscuit has quit [Ping timeout: 480 seconds]
14:30Heyb4r has quit [Ping timeout: 482 seconds]
14:40Heyb4r has joined #asahi-dev
14:42Heyb4r_ has joined #asahi-dev
14:42Heyb4r has quit [Read error: Connection reset by peer]
14:44MajorBiscuit has joined #asahi-dev
14:50Heyb4r_ has quit [Ping timeout: 480 seconds]
14:54Heyb4r has joined #asahi-dev
15:00Heyb4r has quit [Remote host closed the connection]
15:01Heyb4r has joined #asahi-dev
15:09Heyb4r has quit [Ping timeout: 480 seconds]
15:18Heyb4r has joined #asahi-dev
15:20MajorBiscuit has quit [Ping timeout: 480 seconds]
15:24Heyb4r_ has joined #asahi-dev
15:24Heyb4r_ has quit [Read error: Connection reset by peer]
15:25sentinal8473 has joined #asahi-dev
15:26Heyb4r has quit [Ping timeout: 480 seconds]
15:31MajorBiscuit has joined #asahi-dev
15:33sentinal8473 has quit [Quit: Textual IRC Client: www.textualapp.com]
15:34beeblebrox has joined #asahi-dev
15:43millenialhacker has joined #asahi-dev
15:52mazah, looks like M2 has the vgic SError bug fixed... need some more checking, but looking better so far.
15:57mazYup, SError gets nicely delivered to the guest instead of landing on the host. progress!
15:58millenialhacker has quit [Ping timeout: 480 seconds]
15:58millenialhacker has joined #asahi-dev
15:59zimsneexh has joined #asahi-dev
16:26millenialhacker has quit [Ping timeout: 480 seconds]
16:29kettenis_ has quit [Remote host closed the connection]
16:50mazhuh, the E-cores are noticibly faster on M2 than on M1. about 15% quicker for a KVM guest pinned to the small cluster.
17:02svenjannau: https://github.com/AsahiLinux/linux/commits/atcphy-WIP may or may not fix that m1n1 WARN. didn't test it very well yet and still need to rebase it on something more recent though.
17:03svenit also contains the "proper" code to recognize and switch to dp-altmode
17:03svenwon't work with dcpext yet though because the HPD OOB notification won't work yet
17:04sven(note that the role switch quirk changed a bit again, the tipd typec_set_mode path changed and the DTs have svid = <0xff01>; for now because that's what the mux code expects)
17:24amarioguymaz: speedy vgic time :)
17:32MajorBiscuit has quit [Ping timeout: 480 seconds]
17:44nicolas17 has joined #asahi-dev
17:50zimsneexh_ has joined #asahi-dev
17:56zimsneexh has quit [Ping timeout: 480 seconds]
17:56zimsneexh_ is now known as zimsneexh
18:00mazamarioguy: bah, there wasn't much overhead from the traps the first place (interrupts are a pretty rare event anyway)
18:13ChaosPrincessi am trying to trace spi with mini and getting an error "Event checksum error: Expected 0x00000002, got 0xd0decade", after which the mac reboots. Anyone seen something like that?
18:14svenreboots usually happen when you do something either the soc itself or xnu really doesn’t like
18:15svencan you paste the tracer you use somewhere?
18:15millenialhacker has joined #asahi-dev
18:15svenand iirc most of spi goes through this weird SmartIO coprocessor
18:17ChaosPrincessif i comment out the exception code in m1n1, only m1n1 client crashes, while the mac proceeds to boot
18:23jannauChaosPrincess: I don't think I saw that while tracing the keyboard/mouse. the sio tracer in hv/trace_keyboard.py had sharp edges but I can't remember any SPI only issues
18:23ChaosPrincessthe touchpad does not seem to use sio
18:23jannauSPI only is for the keyboard unfortunately not interesting
18:24jannautouchbar?
18:40jannausven: still a warning on powering the apple silicon m1n1 device down: https://paste.debian.net/1261624/
18:41jannaudo you want (the same) tracing?
18:42jannaurebased on asahi-wip but without differences in phy/apple, usb/typec/tipd, usb/dwc3 except for your irq event initialization patch
18:44jannaulet me check your tree directly
18:46sventhe chance in phy/apple are quite important ;)
18:46svenso to reproduce this you just connect a m1n1 device and then shut it down?
18:46svenbecause at least when tying "reboot" in shell.py that didn't trigger anything here
18:46svens/chance/changes/
18:49svenuh, but you have the atcphy changes because it WARNed in atcphy_mux_set_work
18:50svenand it did shut down xhci just before afaict. weird.
18:50jannaupowering it down by long-press on the power button. phy/apple was identical, there were some changes in usb/dwc3 which were probably upstream
18:50jannauphy/apple was identical to atchphy-WIP
18:50svenasahi-wip doesn't have atcphy_mux_set_work yet
18:52sveni'm about to head out but i'll see if I can reproduce it tomorrow with the power button here
18:54jannaucable disconnect seems to trigger it as well when the m1n1 device wasn't detected at all
18:55jannaunow testing with atcphy-WIP directly
18:55lewurm has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
18:56jannaubut I've tested the whole time with identical code in drivers/phy/apple
18:56millenialhacker has quit [Read error: Connection timed out]
18:57zimsneexh has quit [Quit: zimsneexh]
18:59millenialhacker has joined #asahi-dev
19:01lewurm has joined #asahi-dev
19:13millenialhacker has quit [Ping timeout: 480 seconds]
19:18___nick___ has joined #asahi-dev
19:18___nick___ has quit []
19:18riker77 has quit [Quit: Quitting IRC - gone for good...]
19:20___nick___ has joined #asahi-dev
19:27riker77 has joined #asahi-dev
19:41svenif that mux_set_work is already there it should be the latest code. guess I still have a bug somewhere that’s drop a role change event
19:42sven*that drops
19:43psykose has joined #asahi-dev
20:03millenialhacker has joined #asahi-dev
20:08riker77 has quit [Quit: Quitting IRC - gone for good...]
20:11psykose has quit [Ping timeout: 480 seconds]
20:11millenialhacker has quit [Ping timeout: 480 seconds]
20:19riker77 has joined #asahi-dev
20:38millenialhacker has joined #asahi-dev
20:46millenialhacker has quit [Ping timeout: 480 seconds]
20:56psykose has joined #asahi-dev
20:56jluthra has quit [Remote host closed the connection]
20:57jluthra has joined #asahi-dev
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:09leitao has joined #asahi-dev
21:10leitao has quit []
21:20mac456 has joined #asahi-dev
21:36millenialhacker has joined #asahi-dev
21:41dbadams has joined #asahi-dev
21:44millenialhacker has quit [Ping timeout: 480 seconds]
21:49cylm has quit [Ping timeout: 480 seconds]
21:55mac456 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
22:04millenialhacker has joined #asahi-dev
22:19millenialhacker has quit [Ping timeout: 480 seconds]
22:36psykose has quit [Remote host closed the connection]
22:37millenialhacker has joined #asahi-dev
22:42jvzr has quit [Remote host closed the connection]
22:45millenialhacker has quit [Ping timeout: 480 seconds]
22:48millenialhacker has joined #asahi-dev
22:56millenialhacker has quit [Ping timeout: 480 seconds]
23:16millenialhacker has joined #asahi-dev
23:22SSJ_GZ has quit [Ping timeout: 480 seconds]
23:25millenialhacker has quit [Ping timeout: 480 seconds]
…