A monitor or embedded display requires a certain display mode to operate correctly. Monitors often support various modes whereas embedded displays are usually a bit pickier. Display modes specify a combination of parameters, not only the display resolution but also refresh rate, color depth, and signal timings. On personal computers, the monitor passes the supported modes to the connected host system (Extended display identification data, EDID, transmitted through the Display Data Channel, DDC). The operating system presents the available modes to the user, typically as a list of available resolutions since the resolution is the parameter of primary interest. Embedded displays often do not have a dedicated DDC (e.g. parallel RGB, LVDS, or similar display links), and therefore the system needs to be told what exact display resolution and timings have to be supplied.
If there are multiple display modes available (either through EDID/DDC or multiple display modes specified for an embedded display), the system allows choosing between them. In Linux, various subsystems deal with display modes. Depending on the display controller and driver used, different ways of configuring the mode are available. Available interfaces are for instance:
A connected monitor provides the modes it is capable of displaying and its preferred mode through DDC/EDID. The kernel then decides on the mode depending on the capabilities of the monitor and the SoM.
No configuration is needed, a connected monitor provides the modes it is capable of displaying and its preferred mode through DDC/EDID. The kernel then decides on the mode depending on the capabilities of the monitor and the SoM.
The additional command line parameter mxc_hdmi.only_cea=1 limits the modes considered valid to CEA defined ones, e.g. 480p, 720p, 1080p.Some monitors do only work with this parameter set while others do only work without the parameter, however most monitors do work either way.
The Tegra X driver provides (partial) support for the X RandR extension. On the DVI/HDMI output, the Tegra driver supports reading display modes from EDID via the Display Data Channel (DDC). Toradex also enhanced the driver to use the fbdev modedb and kernel argument support for the parallel RGP/LVDS output.
Depending on your display, the kernel-provided modes might not work as expected. Also, some pixelclocks cannot be set very exactly due to hardware restrictions (especially on Tegra 2 based devices). Thus, different timings might lead to different results.
The additional letter M allows to calculate margins using the common timing formula, the letter R calculates reduced margins. If you experience problems with your display, those options might be worth a try. We tested several displays and can recommend the following settings:
The Vybrid DCU driver not only allows selecting the kernel internal modes from the table of modedb.c but also the modes specified in the device tree. This is helpful if multiple modes are specified in the device tree. For instance, the standard device tree carrier board file arch/arm/boot/dts/vf-colibri-eval-v3.dtsi has a set of display specifications for the displays available through the Toradex webshop. One can use the kernel parameters to select one of them:
Note that the panning operation is not executed immediately. The Vybrid's display controller DCU implements a mechanism that makes sure that all configuration changes are synchronized to vertical blanking periods, including the new framebuffer pointer offset (panning). Hence after issuing the ioctl FBIOPAN_DISPLAY requesting the pan to the second framebuffer the first framebuffer could still be scanning out at that time. To make sure the first framebuffer is not scanned out anymore use FBIO_WAITFORVSYNC to wait for the next vertical blanking period. At that point, it is safe to update the first framebuffer. The small test utility fb-test.c illustrates this approach and can be used to test vertical synchronization.
Prior to the updated Dual-Mode Standard release, Dual-Mode cable adaptors were limited to a TMDS clock rate of 165MHz providing support for display resolutions up to 1080p with 60Hz and 24 bits color. In this latest specification, a new Dual-Mode cable adaptor configuration is defined that enables a TMDS clock rate of up to 300MHz. While the DVI standard limits TMDS clock rates up to 165MHz, the HDMI 1.4 specification allows TMDS clock rates up to 297MHz, enabling the support of 1080p 3D at 60Hz, or Ultra HD (4K x 2K) up to 30Hz frame rate.
The RL2455HM is the latest in a series of professional gaming monitors created by BenQ. If you follow competitive gaming, you have most likely seen their monitors being used in various video game competitions throughout the world, most notably in Major League Gaming. BenQ have earned a reputation creating displays where every millisecond counts, and the RL2455HM continues this trend being the official monitor of the 2013 Major League Gaming circuit. While it is advertised as a monitor designed for RTS games, it actually functions exceptionally well for a variety of game genres, including shooters, fighters, and fast-paced action games.
Note: These settings were achieved using an i1 Display Pro, along with X-Rite i1 Profiler and BasICColor software. The GPUs used on the test computer are Nvidia GTX 970s running in SLI configuration, using stock settings. These settings require an additional ICC profile for accuracy. Use these settings at your own discretion, as they may look different on your display.
Adeel Soomro, also known as "Four Wude", has been professionally competing in fighting games since 2008. Using his extensive gaming experience on a casual and professional level, he aims to spread the awareness of input lag existing in today's displays. Having tested over 500 displays for input lag, he hopes that DisplayLag will aid gamers around the world when purchasing the best HDTV or monitor for gaming.
EmulationStation by default runs in full-screen, and may use the old full-screen resolution even through restarts, cutting off a part of its display. For testing purposes, you can temporarily use windowed mode for the current session with:
If you suspect there is an issue with your Samsung TV display, you can perform a TV display test to diagnose the issue. Follow the steps below to test your TV screen or if you need to troubleshoot your screen, follow our step by step guide to perform a TV display settings reset. Read our FAQ on how to use Device Care for more information on TV diagnostics.
df19127ead