setting a custom video mode using DRM/KMS in Linux (tested on raspberry pi 4)

Whether by design or by oversight, it turns out the kms/drm driver architecture used in linux to set the current video mode allows easy selection of custom modes as well. You just stuff the values you want into the mode structure returned by getConnector, and then tell drm to use that mode. Because this is close to the metal you can't just say height, width, and refresh, but need to specify the full timing info like you would using xorg's modelines. In fact, here's some code that takes a xorg compliant modeline and stuffs it into the proper fields of the mode structure. 


drmModeConnector *connector = getConnector(resources);
   connectorId = connector->connector_id;

    // choose a mode (resolution + refresh rate)

    mode_info = connector->modes[modenum]; // array of resolutions and refresh rates supported by this display
    mode = &mode_info;
    dump_mode(mode);

  if (argc == 3)
    {
    mode->type = DRM_MODE_TYPE_USERDEF;

     char flags[5][16] = {0,0,0,0,0};;
   float fclock;
// example: 13.514 720 739 801 858 480 488 494 525 -hsync -vsync interlace dblclk
    sscanf(argv[1], "%f %hd %hd %hd %hd %hd %hd %hd %hd %15s %15s %15s %15s",
   &fclock,
   &mode->hdisplay,
   &mode->hsync_start,
   &mode->hsync_end,
   &mode->htotal,
   &mode->vdisplay,
   &mode->vsync_start,
   &mode->vsync_end,
   &mode->vtotal, flags[0], flags[1], flags[2], flags[3], flags[4]);
   
    mode->clock = fclock * 1000;

         mode->flags = 0;

for (int f = 0; f < 4; f++)  // this could use the array that's used to dump the flags
{
if (strcasecmp(flags[f], "+hsync") == 0)
                mode->flags |= DRM_MODE_FLAG_PHSYNC;
        if (strcasecmp(flags[f], "-hsync") == 0)
                mode->flags |= DRM_MODE_FLAG_NHSYNC;

        if (strcasecmp(flags[f], "+vsync") == 0)
                mode->flags |= DRM_MODE_FLAG_PVSYNC;
        if (strcasecmp(flags[f], "-vsync") == 0)
                mode->flags |= DRM_MODE_FLAG_NVSYNC;

        if (strcasecmp(flags[f], "interlace") == 0)
                mode->flags |= DRM_MODE_FLAG_INTERLACE;

if (strcasecmp(flags[f], "dblclk") == 0)
                mode->flags |= DRM_MODE_FLAG_DBLCLK;
}

  mode->vrefresh = .49 + drm_mode_vrefresh(mode); // looks like this is just for display, since it's an integer it's notused for any real display calculations
snprintf(mode->name, sizeof(mode->name),"%dx%d%c", 
mode->hdisplay, mode->vdisplay,
    (mode->flags & DRM_MODE_FLAG_INTERLACE ? 'i':0)); 

Comments

Post a Comment

Email me

Name

Email *

Message *

Popular posts from this blog

Panasonic TH-42PX75U Plasma TV review: input lag and upscaling tested using the piLagTesterPRO

Image
This 720p Plasma TV from 2008 is very unique and quite nice in many ways. It used to retail for around $1300. If you can find one it's a great choice for retro gaming.  Overview/Image quality This is a plasma TV, which generally means at least the following: nearly infinite viewing angles, and jaw dropping weight. That's true in this case as well. This 42" model weights 75lbs.  At native resolution (720p) this TV crops 20 pixels off the top/bottom and 30 off the sides. 480p/i crops 20 pixels off all sides. Both modes have aliasing, too, though it's not too bad. There's really no excuse for aliasing on a TV this big: you know the panel was designed specifically to be a tv. Why not hit 720p exactly? And as for 480p/i, they could have at least offered a zoomed out mode with black borders and 1:1 pixel mapping. But no such luck. There are zoom/stretch options to crop even more, but none that crop less. While the native resolution supposedly is 1366 x 768 it does accept...
Read more

piLagTester PRO order page

Image
The piLagTesterPRO measures your monitor's input lag and response time. It is a cheap, full featured add-on to the Raspberry Pi; I provide the sensor and required software, you provide the Pi (a $5 pi Zero is more than sufficient). Although it has a DIY aesthetic, it is quite functional and in fact offers quite a lot more features than the commercial alternatives (Leo Bodnar and the Time Sleuth), and has been tested with over 40 TVs, including 4k models .  Here's what it looks like in action: The pi draws a black background, and then roughly once a second displays a set of target rectangles (top/middle/bottom). You place the sensor over the desired target, and the piLagTester measures the monitor's response starting from the moment the frame of video data is sent over the Pi's HDMI port. This is plotted in the graph, which is sideways for space reasons. The lag tester measures two thresholds. In red it shows how long it takes for the monitor to start displaying t...
Read more

A $5 TV Input Lag tester using a Raspberry Pi Zero

Image
High speed monitors are all the rage now, with quoted response times  of 1-4ms. But does that mean that 1-4ms after you make an input (say, jump) you will see that on your screen? No. Often a much bigger issue is  Input lag. This is   the delay between your computer / game console sending a video frame to your display and your display starting to actually show it, and it ranges from 4ms to 80ms. The problem with measuring input lag is that you can't, at least with everyday hardware. The solution for hardware review sites is to purchase dedicated lag testers such as the leo bodnar tester,  timesleuth (both ~$100), or the pi lag tester pro ($40) or use homegrown methods utilizing an oscilloscope ("free" if you already own a $400+ oscilloscope and perhaps a $50k+ engineering degree). Here I introduce a $5 solution (or, "free" if you own the required equipment). What's required: A Raspberry Pi Zero ($5 + S&H from several sources). This single b...
Read more