This is not about X11/xorg, this is text mode/framebuffer stuff only.
You should be at an init level that doesn't have X running.
Sorry, I don't actually know if this will mess up your X configuration as I do not use X.
I've cut down all the steps for brevity; one should know how to compile kernels and move around the system already, etc.
EDIT: THIS IS THE WRONG WAY TO DO THIS.
THE CORRECT WAY IS TO SET THE DTS TO USE "VOPB" INSTEAD OF "VOPL", *NOT* FORCING VOPL TO USE A HIGHER OUTPUT RES.
I WILL REPLACE THE FOLLOWING STEPS WITH THE CORRECT FIX ASAP:
1) Grab the source to your current ayufan kernel
(I'm using linux-kernel-4.4.138-1094-rockchip-ayufan in this demo)
2) tar xf linux-kernel-4.4.138-1094-rockchip-ayufan.tar.gz
3) cd linux-kernel-4.4.138-1094-rockchip-ayufan/drivers/gpu/drm/rockchip
4) Use your favorite editor on rockchip_vop_reg.c
5) Now change the hardcoded limit for rk3399_vop_lit.
Find the vop_data struct for rk3399_vop_lit which starts with this text: static const struct vop_data rk3399_vop_lit {
The property to find and edit within that struct is: .max_output = {2560, 1600}
6) I changed my max_output to this: .max_output = {3840, 2160}
7) Then I recompiled the kernel. For me, that's: make all modules modules_install dtbs_install firmware_install headers_install install -j6
8) Then I manually clean up the mess that postinst.d makes within /boot/extlinux/extlinux.conf
(I literally delete all the lines except for the timeout, menu, label, kernel, initrd, devicetreedir, and append lines for this kernel I just installed)
Worked instantly when I rebooted into the new kernel.
Framebuffer came up in 4K mode and it was GIANT!
Then, when I launched Kodi (which I compiled for DRM with GBM), I was able to whitelist my TV's 4K resolutions (which were never listed before) or even switch the interface to use 4K (I don't suggest doing that) and when I go to play a 4K video, it switches resolution to 4K.
rkmpv at the command line now also switches to 4K resolution for me!
Next up would be for one of us to get some of the VPU pieces working and the rkmpp kernel side working so that 4K and HEVC/x265 videos stop dropping frames.
You should be at an init level that doesn't have X running.
Sorry, I don't actually know if this will mess up your X configuration as I do not use X.
I've cut down all the steps for brevity; one should know how to compile kernels and move around the system already, etc.
EDIT: THIS IS THE WRONG WAY TO DO THIS.
THE CORRECT WAY IS TO SET THE DTS TO USE "VOPB" INSTEAD OF "VOPL", *NOT* FORCING VOPL TO USE A HIGHER OUTPUT RES.
I WILL REPLACE THE FOLLOWING STEPS WITH THE CORRECT FIX ASAP:
1) Grab the source to your current ayufan kernel
(I'm using linux-kernel-4.4.138-1094-rockchip-ayufan in this demo)
2) tar xf linux-kernel-4.4.138-1094-rockchip-ayufan.tar.gz
3) cd linux-kernel-4.4.138-1094-rockchip-ayufan/drivers/gpu/drm/rockchip
4) Use your favorite editor on rockchip_vop_reg.c
5) Now change the hardcoded limit for rk3399_vop_lit.
Find the vop_data struct for rk3399_vop_lit which starts with this text: static const struct vop_data rk3399_vop_lit {
The property to find and edit within that struct is: .max_output = {2560, 1600}
6) I changed my max_output to this: .max_output = {3840, 2160}
7) Then I recompiled the kernel. For me, that's: make all modules modules_install dtbs_install firmware_install headers_install install -j6
8) Then I manually clean up the mess that postinst.d makes within /boot/extlinux/extlinux.conf
(I literally delete all the lines except for the timeout, menu, label, kernel, initrd, devicetreedir, and append lines for this kernel I just installed)
Worked instantly when I rebooted into the new kernel.
Framebuffer came up in 4K mode and it was GIANT!
Then, when I launched Kodi (which I compiled for DRM with GBM), I was able to whitelist my TV's 4K resolutions (which were never listed before) or even switch the interface to use 4K (I don't suggest doing that) and when I go to play a 4K video, it switches resolution to 4K.
rkmpv at the command line now also switches to 4K resolution for me!
Next up would be for one of us to get some of the VPU pieces working and the rkmpp kernel side working so that 4K and HEVC/x265 videos stop dropping frames.