| 15 Jan 2024 |
 K900 | It's literally specified like that | 23:06:27 |
| K900 | Why does a protocol that's digital on both sides have vblank? | 23:06:41 |
| K900 | lol | 23:06:44 |
 FavoritoHJS | In reply to @k900:0upti.me
Why does a protocol that's digital on both sides have vblank? good question actually, modern displays have no electron beam to steer, so why have blanking periods at all unless you really need to multiplex multiple signals onto a single wire? | 23:08:25 |
| FavoritoHJS | +10% bandwidth lifehack | 23:08:52 |
| FavoritoHJS | * +10% bandwidth lifehack[citation needed] | 23:09:00 |
| K900 | It's literally just very overclocked DVI-D, remember | 23:09:05 |
| K900 | That was designed for CRTs | 23:09:11 |
| FavoritoHJS | * +10% bandwidth lifehack [citation needed] | 23:09:15 |
| K900 | And now I wonder how many DP implementations in the wild would actually explode if you tried to interleave audio and video packets at less than one frame per packet | 23:09:59 |
| K900 | I'm going to guess a lot | 23:10:07 |
| K900 | Also, yeah, the HDMI Forum has some very funny rules when it comes to IP protection | 23:11:19 |
| FavoritoHJS | right, that reminds me, how far can i cut down the blanking periods on this laptop? | 23:11:31 |
| K900 | Which is why we still don't have full speed HDMI 2.1 on AMD on Linux | 23:11:36 |
| K900 | Because they can't put it in the driver | 23:11:46 |
| K900 | Can you find it in 10 seconds on 4pda? Yes | 23:11:56 |
| K900 | Is it literally just the timings from 2.0, which are known publicly, but sped up by like 50%? Also yes | 23:12:26 |
| K900 | Did the HDMI Forum decide it's critical IP that needs protection? You bet | 23:12:44 |
| FavoritoHJS | maybe try suggesting to add an overclocking option that just so happens to max out at 2.1 spec | 23:13:13 |
| K900 | Nvidia runs it in firmware | 23:13:22 |
| FavoritoHJS | technically not 2.1 but might as well be | 23:13:29 |
| K900 | Intel has a separate Realtek DP to HDMI converter chip on the board | 23:14:48 |
| K900 | Yes they actually did that | 23:15:00 |
| FavoritoHJS | if even intel at their peak couldn't be arsed to untangle what the fuck is going on at the HDMI Forum you know you went too far | 23:16:52 |
| K900 | I mean I wouldn't call Intel's GPU division "peak" - not yet anyway | 23:17:28 |
| K900 | But this was definitely a "we're so fucking done here" engineering decision | 23:17:51 |
| FavoritoHJS | were you talking about the (electric) arc gpus or integrated craphics? | 23:18:35 |
| FavoritoHJS | if it's the latter i'll count it as "intel at their peak" as that would have meant one less chip on the board | 23:19:18 |
| FavoritoHJS | * if it's the latter i'll count it as "intel at their peak" as that would have meant one less chip on the motherboard | 23:19:23 |
| K900 | I'm talking about the dedicated GPUs | 23:21:02 |
