Difference between revisions of "Pi:console resolution"
(→Prerequisits) |
(→Display geometry) |
||
| Line 42: | Line 42: | ||
<code>-g, --geometry ...</code> set all geometry parameters at once | <code>-g, --geometry ...</code> set all geometry parameters at once | ||
| − | <code>-match</code> | + | <code>-match</code> set virtual vertical resolution by virtual resolution |
| − | + | ||
=== Display positioning === | === Display positioning === | ||
<code>-move <direction></code> move the visible part (left, right, up or down) | <code>-move <direction></code> move the visible part (left, right, up or down) | ||
Revision as of 13:43, 5 January 2024
Contents
Abstract
`nextpi-console_resolution` is designed to allow easy manipulation of the resolution and colourdepth of the Spectrum Next "Debug Video" port.
Prerequisits
- NextPi Version: 1.92D
- Hardware Setup: Monitor attached to "Debug Video" port on Spectrum Next.
Backend
- Binary: fbset
- Source: https://github.com/Distrotech/fbset
Options
General
-h, --help display this usage information
--test don't change, just test whether the mode is valid
-s, --show display video mode settings
-i, --info display all frame buffer information
-v, --verbose verbose mode
-db <file> use custom resolution database (default is /etc/fb.modes)
Display geometry
-xres <value> horizontal resolution (in pixels)
-yres <value> vertical resolution (in pixels)
-vxres <value> virtual horizontal resolution (in pixels)
-vyres <value> virtual vertical resolution (in pixels)
-depth <value> display depth (in bits per pixel)
-nonstd <value> select nonstandard video mode
-g, --geometry ... set all geometry parameters at once
-match set virtual vertical resolution by virtual resolution
Display positioning
-move <direction> move the visible part (left, right, up or down)
-step <value>: step increment (in pixels or pixel lines - default is 8 horizontal, 2 vertical)
Potential Features
There are no anticipated new features planned for this CLI API, or reasons expected to require to change the backend.
The backend supports many more options than those listed but those generally not applicable to modern HDMI screens have been ommitted from this documentation for that reason.