3 ms·
> Just like most digital interfaces nowadays, DisplayPort sends its data in packets. This might sound like a reasonable expectation, but none of the other popul
by crazygringo 3y ago
> Just like most digital interfaces nowadays, DisplayPort sends its data in packets. This might sound like a reasonable expectation, but none of the other popular video-carrying interfaces use packets in a traditional sense – VGA, DVI, HDMI and laptop panel LVDS all work with a a stream of pixels at a certain clock rate.
Funny, a stream of data at a constant rate makes much more sense to me intuitively than packets, specifically for uncompressed video.
Are there any downsides to packetization, like increased latency or dropped frames or anything? Or not really, is it all upsides in being able to trivially combine multiple data streams or integrate easily into hubs?
- tverbeure 3y agoLatency is limited to the amount of buffering that's present in the interface logic (on sides). In the case of regular DP, there's just a few FIFOs and pipeline stages, so the latency is measured in nanoseconds. When using display stream compression (DSC), there's a buffer of 1 line, and a few FIFOs to handle rate control. At the resolution for which DSC is used (say, 4K/144Hz), the time to transmit a single line is around 3us. So that's the maximum additional latency you can expect.
- wtallis 3y ago> Funny, a stream of data at a constant rate makes much more sense to me intuitively than packets, specifically for uncompressed video. Sure, until you start trying to design the transceivers and realize that supporting two or three fixed standard data rates is a lot simpler than supporting a continuously-variable clock speed. Every other high-speed digital interface operates at just a few discrete speeds: SATA/SAS, PCIe, Ethernet, USB. The fact that DVI and HDMI were such a shallow digitization of VGA's racing-the-beam meant features like variable refresh rate (Gsync/Freesync) showed up far later than they should have. If we hadn't wasted a decade using CRT timings (and slight modifications thereof) to drive LCDs over digital links, it would have been more obvious that the link between GPU and display should be negotiated to the fastest data rate supported by both endpoints rather than the lowest data rate sufficient to deliver the pixels.
- ansible 3y ago> ... If we hadn't wasted a decade using CRT timings (and slight modifications thereof) to drive LCDs over digital links ... Don't forget the decade or so (late 1990's to early 2000's) where we were driving LCDs over analog links (VGA connectors). I had purchased a pair of Silicon Graphics 1600SW monitors back in the day, which required a custom Number Nine graphics card with an OpenLDI display interface. It was many years since those were introduced to the market that DVI finally started becoming commonplace on PC graphics cards. Using the mass-market LCD monitors in the late 1990's was a frustrating affair, where you had to manually adjust the timing synchronization of the analog signal.
- samtho 3y ago> Funny, a stream of data at a constant rate makes much more sense to me intuitively than packets, specifically for uncompressed video. There is a data rate floor for how fast the device that outputs must meet. We’ve surpassed this (due to optimization at the silicon level, designing hardware who’s sole job it is to send bursts of data) and we end up running out of data in the buffer periodically because it’s just so fast. Because analog is real time, you can squeeze much else in that data stream but with digital, we are afforded the luxury of packet switching instead of that line being idle, we can pump even more down the linen. > Are there any downsides to packetization, like increased latency or dropped frames or anything? Or not really, is it all upsides in being able to trivially combine multiple data streams or integrate easily into hubs? If I recall correctly, the timing and data rates is all prearranged based on reported capacity and abilities of the receiving device and it won’t even attempt to support multiple streams if it is incapable of doing so or the data channel established cannot fully support the bandwidth required.
- willis936 3y agoIf you didn't packetize then the receiver would never recover line coding state when a single symbol is missed. The rest are incidental details.