#asahi-dev · 2024-05-07 14:44
svenmaybe just testing the new process node?#asahi-dev · 2024-05-07 14:44
sventhis looks more like a m3 2.0 tbh#asahi-dev · 2024-05-07 14:43
sventhere’s still a chance I can finish support before they release a chip with new capabilities #asahi-dev · 2024-05-07 14:43
svenphew, nothing about tbt #asahi-dev · 2024-05-07 14:37
jannauhttps://www.apple.com/newsroom/2024/05/apple-introduces-m4-chip/#asahi-dev · 2024-05-07 14:26
j`eymaybe asahi should just support even numbers from now on or something :P#asahi-dev · 2024-05-07 14:26
svenuh oh#asahi-dev · 2024-05-07 14:19
jannausigh, m4#asahi-dev · 2024-05-07 11:48
chadmedoh well there goes that idea#asahi-dev · 2024-05-07 11:48
chadmedtvos uses dolby mat and macos doesnt even pretend to support bitstream formats at all #asahi-dev · 2024-05-07 11:48
chadmedoh ffs#asahi-dev · 2024-05-07 10:47
chadmed_using that also gets us friendly identifiers for free once displayid is wired up #asahi-dev · 2024-05-07 10:46
chadmed_seems possible to rework the firmware string parsing helpers to not take snd_interval/snd_mask for the sieve and just look for whatever the codec has requested. if it cant find it just throw an error back.#asahi-dev · 2024-05-07 10:44
chadmed_i still think this could and should be reworked as an asoc driver. the only thing that doesnt really make sense to me is the avep element parsing. aiui DCPAVAudioService reports the sink's supported capabilities and the driver is putting constraints on the pcm at runtime based on the connected sink#asahi-dev · 2024-05-07 10:41
chadmed_interestingly the samples were dumped _after_ forcing a hard shutdown and my tv played them as the screen went black... dunno how that works#asahi-dev · 2024-05-07 10:41
chadmed_jannau: https://0x0.st/X88Q.txt sio explosion when attempting to use iec958 passthrough in vlc#asahi-dev · 2024-05-06 07:44
chadmed_*sigh* i should boot the 14" pro up more often#asahi-dev · 2024-05-06 07:43
chadmed_>Emerging (44 of 328)#asahi-dev · 2024-05-06 07:00
chadmed_every sink _should_ gracefully handle it#asahi-dev · 2024-05-06 07:00
chadmed_aiui it's up to the sink to parse and decode whatever bitstream the source sends it, which is why linux can get away with iec958 being a passthrough catch-all "digital" mode#asahi-dev · 2024-05-06 06:58
chadmed_(adding SNDRV_PCM_FMTBIT_IEC958_SUBFRAME_LE to supported formats and sending it)#asahi-dev · 2024-05-06 06:57
chadmed_im about to do something like that :p#asahi-dev · 2024-05-06 06:56
jannauI would assume it does. I suppose someone has to sit in front of a TV / AV amplifier and trace what macos/dcp does#asahi-dev · 2024-05-06 06:52
chadmed_if it's just pcm frames we might not even need to do anything extra other than that#asahi-dev · 2024-05-06 06:51
chadmed_so we need to tell alsa that it supports the iec958 pcm formats and figure out how to make dcp do that (assuming it supports it [which it should]) #asahi-dev · 2024-05-06 06:49
chadmed_otherwise apple are bit-banging dolby, dts, etc #asahi-dev · 2024-05-06 06:49
chadmed_it should support at least passing through the bitstream to whatever is on the other end of the hdmi out#asahi-dev · 2024-05-06 06:42
jannaubitstream format would be pointless if they need to decoded first. DCP has no audio encoders (I hope)#asahi-dev · 2024-05-06 06:38
jannauI think bitstream formats are simply not yet looked at. I think povik tested only with monitor(s) which support only stereo pcm#asahi-dev · 2024-05-06 06:34
chadmedor is it more that we feed DCP PCM and it handles the actual bitstream format in firmware? #asahi-dev · 2024-05-06 06:34
chadmedright okay, didnt realise we _only_ support PCM. thought that was just the driver#asahi-dev · 2024-05-06 06:33
jannauchadmed: it didn't looked like a good fit. we query channel maps / rates from dcp. we only support PCM. I'm sure povik looked at hdmi-codec and decided against using it (initially)#asahi-dev · 2024-05-06 05:50
chadmedcurrently its being enumerated as a bare AVOUT jack which is why it gets picked up as built-in analog audio #asahi-dev · 2024-05-06 05:43
chadmedjannau: there is an asoc codec that is essentially just an hdmi helper. should we rewrite the dcp audio stuff as an asoc driver to make use of that? it seems to be mostly what we're looking for, we could even attach each dcp instance to macaudio and just leave it inactive if theres no display attached to it? #asahi-dev · 2024-05-05 14:58
zzywysmok, thanks#asahi-dev · 2024-05-05 14:58
jannauit not there on purpose#asahi-dev · 2024-05-05 14:57
zzywysmjannau: that line "vidconsole_set_cursor_visible(dev, true, x, y, 0);" does not appear in that tag based on reviewing it in github's web interface, do you mean that that commit isn't actually necessary?#asahi-dev · 2024-05-05 14:55
jannauzzywysm: no#asahi-dev · 2024-05-05 14:54
zzywysmjannau: your u-boot tag asahi-v2024.04-1 is missing your commit "video: console: Enable cursor" from your asahi-vidconsole-kbd-fixes, it may be missing more#asahi-dev · 2024-05-05 09:52
jannauI've pushed asahi-6.8.8-3 and asahi-6.8.9-1 to asahi-wip#asahi-dev · 2024-05-04 17:17
jannaunicolas17: OS firmware 13.5 / system firmware 14.5 beta#asahi-dev · 2024-05-04 17:16
nicolas17jannau: 13.5 or 14.5?#asahi-dev · 2024-05-04 10:53
jannaulol, no. 13.5 just dropped two callbacks and IOMFB::MemDescRelay::release_descriptor is now D454#asahi-dev · 2024-05-04 09:04
jannau50Hz would be so much nicer to debug vsync issues#asahi-dev · 2024-05-04 09:04
jannaudcp started to use those callbacks with recent system firmware. I think there was a report with 14.2 or later and I'm seeing that with 14.5 beta when switching the refresh rate to 50Hz on j314c#asahi-dev · 2024-05-04 09:01
jannauI see "address" like 0x138018000, 0x128008000 so either scaled or below the MMIO start#asahi-dev · 2024-05-04 08:58
jannaunot convinced about unk_addr and unk_flags#asahi-dev · 2024-05-04 08:58
jannauI have "D453 = Callback(mem_desc_id, "withAddressRange", unk_addr=ulong, size=ulong, unk_flags=uint, task=uint64_t, dva=OutPtr(ulong), dvasize=OutPtr(ulong))"#asahi-dev · 2024-05-04 08:57
jannaumarcan: did you ever look at dcp 'D453 MemDescRelay::withAddressRange()' was that what was used in the ios exploit via dcp?