* Support enabling VRR on displays that advertise it
* Disable SPD and Spare packet registers when they aren't needed. Update ini
Co-authored-by: Zakk <zakk@rsdio.com>
vertical scale and use the minimum.
vscale_mode has been changed to make it more reliable.
vscale_mode=4 - Generate modes that match the cores aspect ratio.
Generally better, will work with more cores and produce most optimal
resolutions, but will not be compatible with displays that always
stretch the image to fill.
vscale_mode=5 - Generate modes that match the original display aspect
ratio, if the core needs a wider aspect then the resolution is not
changed. Compatible with a wider range of displays.
Updated INI with a clearer description.
Removed mode 6 since it was not being used and adjusting display width
doesn't enable integer horizontal scaling.
uh undo
Send pixel repetition as high bit of video width
Half linux framebuffer size when PR is in use
If a modes width is > 2048 then use pixel repetition
Add video_mode 14 2560x1440.
Fallback to mode 8 if core doesn't support PR
video_info wasn't being updated correctly when `force` was set, it was getting
overridden by the previous value because the `res_changed` check was
false.
Both modes ensure there is enough horiztonal resolution to fit the core.
They do this by reducing the vertical resolution as needed. Mode 5 keeps
the horizontal resolution fixed, which uses more bandwidth but reduces
the amount of resolution switches that can occur and prevents the OSD
from getting to narrow in rotated arcade cores.
Initialize the video_info with the current data if the fb_crc changes to
ensure it has valid data for the resolution if the resolution has not
changed.
Cores with Directvideo and composite sync don't seem to need
VSync aligned to HSync when pixel repetition is disabled which
saves time and effort adjusting cores.
The polarity setting is shared between analog and digital output, so
changing it when calculatinga video mode can interfere with analog
video output. If someone has a need to use a specific polarity they
can specify it as part of the video_mode.
Integer Resolution Scaling
Generate a video mode whose vertical resolution is an integer multiple
of the cores vertical resolution. The video mode set via the
`video_mode` parameter is considered the maximum resolution. There are
two modes of operation: vscale_mode=4 - Both vertical and horizontal
resolution are modified. The horizontal resolution is scaled in
propotion to the vertical, so the aspect ratio is maintained. This will
be most suited to VGA CRTs that expect a specific aspect ratio signal.
vscale_mode=5 - Only the vertical resolution is modified. This will be
suitable for most modern LCD/OLED displays. The additional horizontal
resolution provides more space for wide aspect ratio cores.
Video Mode Calculation
CVT timing calculations are used to generate the modified video modes
for Interger Resolution Scaling, this mode generation is also exposed as
an additional way to specify video modes in the MiSTer.ini. Modes can be
specified with just the width, height and refresh rate:
`video_mode=1920,1200,60`. Whether to use the original CVT or the
reduced blanking CVT-RB timings can be specified with an optional flag,
e.g. `video_mode=1024,768,60,cvt`. Additionally the sync polarities can
also be expressed using flags now, e.g.
`video_mode=1280,110,40,220,720,5,5,20,74250,+hsync,-vsync`
Code Changes
More functionality was broken out of `video_mode_adjust`.
`video_mode_select` determines what the correct base video mode is based
on the timing and vsync_adjust configuration. The mode selected there is
then passed to `video_resolution_adjust` which modifies it based on the
integer resolution scaling selected. Other than that the functionality
of `video_mode_adjust` remains the same.
The `video_calculate_cvt` function was added to calculated video mode
timings.
`parse_custom_video_mode` was changed to support the additional flags.
It now uses `str_tokenize` to split up the input string so it is more
easy to manage the different variations of parameter counts allowed for
the modes.
`vmode_custom_param_t` was added to alias the items in the
vmode_custom_t instead of using raw array indexing everywhere.
`str_util.h/.cpp` added to provide some safer and easy to use string
functions. `strcpyz`, `strncpyz`, `sprintfz` all ensure that the
resulting string is null terminated and doesn't overrun memory.
* Override configuration based on video mode
Configuration options can now be overridden based on the core's video
mode.
The config parser now supports sections with names in the format
"video=WIDTHxHEIGHT[@VREFRESH]". When a core changes video mode, MiSTer
reloads the config file and checks for a section matching the new mode.
If one is found, the options in the section override options in the
MiSTer/core sections.
MiSTer will look for a section matching the width, height, and vertical
refresh rate first. If none is found, it will fall back to a section
matching the width and height but not specifying a refresh rate. If
there is still no match, no overrides will be used.
Also, VREFRESH must match exactly the output from video_info or the
logs. To match 720x400 31.48KHz 70.1Hz, the section title would need to
be [video=720x400@70.1].
* Move video section variables out of cfg_t
Include sync polarities in the UIO_SET_VIDEO command. Polarities are
specified in the high bits of the hsync and vsync values. 0 is
negative, 1 is positive.
Horizontal and vertical polarities can optionally be included as two
numbers at the end of custom modes. Again, 0 is negative, 1 is
positive.
Change filter reading code so that it stores all data as if it had 64 phases.
Support "adaptive" keyword in filter files which contain a second set of adaptive filters.
Send filters to core in one of the three supported formats.
Co-authored-by: Alexey Melnikov <pour.garbage@gmail.com>
