-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for screens larger than 2048x2048 #141
Comments
Care to submit a tested patch to the dri-devel mailing list? I don't have 4k hw to test against. |
Hi, Simple change of values in vc4_kms.c to 4096x4096 is not sufficient to make it work. It allows me to create a new custom resolution using
But this fails with error:
This modeline is working for me with fbturbo_dev and increased hdmi_pixel_freq_limit. Any idea on why this is failing? |
We limit the pixel clock in vc4_hdmi_encoder_mode_valid() -- perhaps that is it? Enabling drm.debug can help see where things are failing (sudo zsh -c "echo 0x1e > /sys/module/drm/parameters/debug") |
That could be it, thank you for suggestion. Will try tomorrow. |
After increasing pixel clock limit, I can apply that modeline, but it crashes driver and X server with following output in dmesg:
Last line with error about buffer allocation wasn't there after second attempt to apply that modeline, so it may not be related to this problem. |
@jiridurdis Looks like you are using the Foundation kernel, are you able to build a recent mainline version like 4.19-rc8 or at least 4.18? |
Still crashing on vanilla 4.18.14:
It does not work in 4.19-rc8 either, but it behaves differently. This is what I see during boot:
No errors after activating modeline using xrandr, but still no output. There is interesting difference in
With vc4, after applying modeline with
HDMI clocks are very close to limits that i set in both cases. Pixel clock with framebuffer is equal to my |
Hi,
I believe that while Pi is suitable for video playback up to 1080p only, it still would be nice to support larger screens for other not-so-demanding scenarios. At the moment, maximal screen size is hardcoded to 2048x2048 in vc4_kms.c.
Pi is capable of 4K (3840x2160@25Hz) output over HDMI (using fbturbo and custom hdmi_cvt or hdmi_timings line in config.txt), which is totally OK for displaying dashboards, demos, slideshows etc.
The text was updated successfully, but these errors were encountered: