Pro: this firmware update might fix this one bug I've had with my monitor.
Con: I have to wonder how on earth we have found ourselves in a world where monitors have firmware updates.
@jasonmalinowski idk, decoding the blizzard of HDR standards and running local dimming algorithms, doing VRR things, decoding DSC.... monitors have a reasonable amount of compute doing reasonable things these days
@malwareminigun @jasonmalinowski So far all I can say is my laptop crashed when going to sleep. Related? Who knows!
Hector Martin (@[email protected])

OMG how are some monitors this broken. I had a report from a user of a monitor that stops working after a screen poweroff/poweron. It turns out that when you power off the monitor at the screen and then power it on, it *glitches the HPD signal* which causes an extremely fast disconnect/reconnect cycle, which triggers some race conditions in our display stack/firmware interaction (I think). But it gets worse. If you sleep the screen in software, then wake it up again... it does the same thing! After the Mac starts sending the display a video signal again after a wakeup, the display *vanishes and then comes back* and then the Mac has to do a whole powerdown/powerup and modeset cycle again! On macOS, this causes excessively slow wake-up times, but at least the flow does work there and it does come back eventually. This is also a consequence of the lack of HPD debouncing in Apple's DCP firmware - if it ignored these fast glitches (which are not unique to this monitor, it seems like a rather pervasive problem and I know at least AMD cards debounce the signal) then none of this would happen. Why are monitors and display stacks this messed up...

Treehouse Mastodon
@malwareminigun @jasonmalinowski Oh that thread is brilliant. Good to know it’s not just me who has had to reboot my monitors with the power cable. (At least Dell fixed that one…)
@jasonmalinowski i had a usbc to hdmi cable that needed a firmware update to make it work better