#asahi-dev · 2026-06-27 10:32
integralpilothere, pushed the commit: https://github.com/IntegralPilot/linux2/commit/ebad5b03d3924652c081b9e635e1c65f8eb0236b#asahi-dev · 2026-06-27 10:24
sofusit does not look that way#asahi-dev · 2026-06-27 10:23
JamesCalligeros[m]You didnt get one for each write to the mbox?#asahi-dev · 2026-06-27 10:22
sofusJamesCalligeros[m]: its only for debugging, i think im only getting one interrupt??#asahi-dev · 2026-06-27 10:21
integralpilotjannau: you were sending a new M3 dts patch upstream when -rc1 drops right? is it okay if you include the t8122 i2c fixes in that? ill push now#asahi-dev · 2026-06-27 10:21
JamesCalligeros[m]Perhaps better to send either like a log msg id that can then be referenced from the blob or just use the ring buffer#asahi-dev · 2026-06-27 10:20
JamesCalligeros[m]Idk if using the mailbox like that is a good idea. We will get a lot of interrupts#asahi-dev · 2026-06-27 10:20
sofusoh wow cool, thanks#asahi-dev · 2026-06-27 10:19
chaos_princesshttps://lore.kernel.org/asahi/376C9BD3-2F41-4511-BE52-1B8468FE2CB3@live.com/#asahi-dev · 2026-06-27 10:16
sofusbehold: https://pastebin.com/A2Mgz48Z#asahi-dev · 2026-06-27 10:14
chaos_princessi do not know how that works#asahi-dev · 2026-06-27 10:14
JamesCalligeros[m]Is that what rtk syslog does?#asahi-dev · 2026-06-27 10:11
chaos_princessif you are going with packing into an int, what you could do is put them into a dedicated section with the linker commands, and then have the printf-equivalent write pointers to syslog. Linux side will then look up the message in the fw blob#asahi-dev · 2026-06-27 10:06
JamesCalligeros[m]I just sent the one, read the log then acked#asahi-dev · 2026-06-27 10:05
sofuscm3 base should just be the same as SP actually#asahi-dev · 2026-06-27 10:04
sofusi just send 2 irq's to mbox 0#asahi-dev · 2026-06-27 10:03
JamesCalligeros[m]I had a loca kernel branch that acked the irq but i had to go out (hence matrix acc) so didnt get around to parsing the log message#asahi-dev · 2026-06-27 10:03
JamesCalligeros[m]Lets gooooooo#asahi-dev · 2026-06-27 10:02
sofusit speaks :p avd 286000000.avd: cm3: helo: word#asahi-dev · 2026-06-27 09:50
JamesCalligeros[m](And get rid of the command and completion buffers if you dont want to go down the route i was thinking of)#asahi-dev · 2026-06-27 09:48
JamesCalligeros[m]But take whatever you want#asahi-dev · 2026-06-27 09:48
JamesCalligeros[m]sofus: youll have to play with the memmap, i forgot where the cm3 sram base is so i just kept adding offset to the base until it stoped breaking interrupt handlers#asahi-dev · 2026-06-27 09:37
jannauchaos_princess suggested that earlier#asahi-dev · 2026-06-27 09:31
sofusalthough if we could pack messages into an int it would be waay easier#asahi-dev · 2026-06-27 09:31
sofusactually i like the syslog think, im gonna steal that#asahi-dev · 2026-06-27 09:26
JamesCalligeros[m]fwiw free to discard all of my opinions and just do whatever, i have no idea what im doing#asahi-dev · 2026-06-27 09:26
JamesCalligeros[m]Nice#asahi-dev · 2026-06-27 09:20
sofusre avd-fw, im gonna start just implementing piodma stuff and the go forward from there#asahi-dev · 2026-06-27 09:05
chaos_princessyea, just remove the message then, it is useless#asahi-dev · 2026-06-27 09:05
chaos_princessoh, so they are now sending it for general battery updates?#asahi-dev · 2026-06-27 09:02
sofusi know, it was just if the event was unkown#asahi-dev · 2026-06-27 09:01
JamesCalligeros[m]nonsense caused by smc firmware, it’s harmless and will be fixed#asahi-dev · 2026-06-27 09:00
sofuseach time the battery percentage goes one up or down the message is logged#asahi-dev · 2026-06-27 08:59
sofussomething unrelated, i think its safe to remove the 'Battery status is OK?' message from macsmc-power https://pastebin.com/1V7qsKbF#asahi-dev · 2026-06-27 08:52
JamesCalligeros[m]Yeah we already support semiplanar#asahi-dev · 2026-06-27 08:51
sofusjannau: maybe? But that does not work#asahi-dev · 2026-06-27 08:50
jannaudcp can scan semi-planar surfaces as well so no issue there#asahi-dev · 2026-06-27 08:49
JamesCalligeros[m]It would be cool to support planar yuv. DCP can scan them out with some magic combination of iosurface values which is not a common thing aiui#asahi-dev · 2026-06-27 08:46
jannauisn't that V4L2_PIX_FMT_NV20? see https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/pixfmt-yuv-planar.html#asahi-dev · 2026-06-27 08:39
sofusi dont now a lot of things about pixel formats so take that with a grain of salt#asahi-dev · 2026-06-27 08:39
sofusP210#asahi-dev · 2026-06-27 08:37
jannauignoring interchange compressed surfaces#asahi-dev · 2026-06-27 08:37
jannauwhat do we need which isn't present yet in v4l2#asahi-dev · 2026-06-27 08:36
jannauI'm at a stage where this could a millionm different things. I would the combination to support nv12 just fine#asahi-dev · 2026-06-27 08:36
sofusif we could change it we would not need to add a new pixel format to v4l2#asahi-dev · 2026-06-27 08:35
jannaudon't spend effort on it, I'm asking because I saw an error while testing mpv/ffmpeg/vaapi with libva-v4l2-request#asahi-dev · 2026-06-27 08:35
sofusfor sure its something in the instruction stream then, i would just need to trace macos doing it (i think)#asahi-dev · 2026-06-27 08:33
jannauI'd say it usually is. I think videotoolbox supports it.#asahi-dev · 2026-06-27 08:31
sofusis something like that normally configurable? #asahi-dev · 2026-06-27 08:30
jannauno, nv12 is semi-planar. it has an Y plane and an interleaved CbCr plane