4K @ 60Hz (2160p60) distro support?

[spawnflagger]

Hello,
  The "Software Images" wiki page has a table that mentions 30Hz refresh for 3840x2160 resolution, but after searching, it's still not clear whether or not there's a Linux distro that supports this full resolution @60Hz.  Can someone confirm that this is working?
(I know the HW spec says HDMI 2.0, so it's just a question of drivers and software).

Also, if it supports 2160p60, does it work at RGB444 chroma subsampling?  (not just YUV420 or YUV422)

Not worried about HDR10- I just want to have a lot of xterm windows open at once (so that rules out Android), and small text looks pretty bad at YUV420.
(I know 30Hz is OK for text too, but since my monitor supports 60Hz, I'd prefer it)

Thanks in advance!

[dkryder]

you might want to check with ayufan on chat. he does not check forum as much as he is logged onto chat.

[mcerveny]

Now 2160p60 works only with YUV420 output format (Pixel Clk: 594MHz/TMDS Clk: 297MHz).
For example YUV420/10bit (Pixel Clk: 594MHz/TMDS Clk: 371.25MHz) does not work (rockchip probably does not ever test it (blocked by bug)).
RK3328 does not support TMDS clk more then 371.25MHz.

[spawnflagger]

you might want to check with ayufan on chat. he does not check forum as much as he is logged onto chat.

Thanks for the tip, got this reply from #Rock64 IRC :

<lukasz> spawnflagger: in latest Bionic and LibreELEC images, yes

[spawnflagger]

Now 2160p60 works only with YUV420 output format (Pixel Clk: 594GHz/TMDS Clk: 297GHz).
For example YUV420/10bit (Pixel Clk: 594GHz/TMDS Clk: 371.25GHz) does not work (rockchip probably does not ever test it (blocked by bug)).
RK3328 does not support TMDS clk more then 371.25GHz.

Thanks for the info!

If possible, can you test this image while running at 3840x2160 @ 30Hz?

• instructions:  http://www.geeks3d.com/20141203/how-to-q...4k-uhd-tv/
  
• direct image link: http://www.ozone3d.net/public/jegx/20141...-4k-tv.png
  

Are the bottom 2 lines of text legible?

[mcerveny]

I tested 4k@60 (YUV420 not HDR, "bbb-3840x2160-cfg02.mkv") with mpi_dec test. HDR ("LG Chess 4K Demo.mp4") and HLG ("LG Cymatic Jazz 4K Demo.ts") test are decoded ~60FPS but output only with 4k@30 output (forced in extlinux.conf) to LG TV OLED without problem. Check actual output chain with:

Code:

# cat /sys/kernel/debug/dw-hdmi/status
# cat /sys/kernel/debug/dri/0/summary

[spawnflagger]

If the RK3328 TMDS clock is indeed limited to ~371MHz (hardware limitation, not just a bug in the driver), then they should not advertise the Chip specs as having HDMI 2.0a.
They would need at least 533MHz TMDS clock (for reduced blanking video modes), and more like 594MHz (standard 60Hz).  If true, RK3328 really should be advertised as HDMI 1.4b.

(it's also possible that the Rock64 implementation introduced some clock limit that's not inherent to the chip, but rather some PCB capacitance, etc., that limits it)

also a clarification:  I'm only referring to the 4K refresh rate capability of the graphics chip, not the CPU/GPU/VPU frame rate decoding capability with any codec.  It's impressive that it can decode 4K content at or near 60fps, but pointless to do so at any frame rate greater than the refresh rate.  There's still a lot of movie content that is 24fps, so it's useful to set display resolution of 3840x2160@24Hz in those cases, but that resolution spec was part of HDMI 1.4, back in 2009...

[mcerveny]

(it's also possible that the Rock64 implementation introduced some clock limit that's not inherent to the chip, but rather some PCB capacitance, etc., that limits it)

This is the Question. Pine64 should clarify this problem. There is only few "marketing" public documents.

also a clarification:  I'm only referring to the 4K refresh rate capability of the graphics chip, not the CPU/GPU/VPU frame rate decoding capability with any codec.  It's impressive that it can decode 4K content at or near 60fps, but pointless to do so at any frame rate greater than the refresh rate.  There's still a lot of movie content that is 24fps, so it's useful to set display resolution of 3840x2160@24Hz in those cases, but that resolution spec was part of HDMI 1.4, back in 2009...

Not exactly true. Now you can decode and display in 60FPS (of cause in YUV420, TMDS Clk: 297MHz) and after resolving some problems HDR/HLG (of cause in YUV420-10bit, TMDS Clk: 371MHz). Rock64 is capable of sending "frame metadata" to support static HDR (HDMI2.0a) and HLG (HDMI2.0b).

[spawnflagger]

Not exactly true. Now you can decode and display in 60FPS (of cause in YUV420, TMDS Clk: 297MHz) and after resolving some problems HDR/HLG (of cause in YUV420-10bit, TMDS Clk: 371MHz). Rock64 is capable of sending "frame metadata" to support static HDR (HDMI2.0a) and HLG (HDMI2.0b).

Yes, you are correct.  I realize I'm in a small minority that would want to use this for text rather than full-motion video.  There's no doubt the RK3328 is designed & marketed for Android STB.
YUV420-10bit feels silly though - lets take away 75% of the color information out of the frame, then increase the depth 25%.... Any 10-bit 4K panel that supports HDR10 or Dolby Vision (that I've ever seen) supports all the HDMI 2.0 resolutions (TMDS 594MHz).  I have seen cheaper UHDTVs that support HDR10, but only have 8-bit panels, but those are also silly in my opinion.

[mcerveny]

YUV420-10bit feels silly though - lets take away 75% of the color information out of the frame, then increase the depth 25%.... Any 10-bit 4K panel that supports HDR10 or Dolby Vision (that I've ever seen).

Color informations are shared for 2x2 pixels not dropped. Yes, I have highend LG OLED (with HDR+HLG+DolbyVision) and all samples (HDR+HLG+DolbyVision) are encoded "yuv420p10le". Check specification (with support profiles of RK3328) for HEVC Main10 and H264 Hi10P that are supported only in 4:2:0