PBXGA graphics card
Table of Contents
General description
Charon-AXP supports emulation of PBXGA graphics card(s) by direct virtualization and provides a virtual console for displaying graphics.
The console starts automatically upon starting the emulator. Its resolution is 800 x 600 by default.
Support for AXP graphics is provided with two components:
- emulation of PBXGA PCI graphics adapter and
- emulation of display unit (display unit is emulated with separate executable PBXGA_TV)
Emulated cards
- PBXGA_AA emulates 8bpp graphics card (256 colors, pseudo-color) with 4MB frame buffer - ZLXp-E1
- PBXGA_BA emulates 24bpp graphics card (16M colors, TrueColor) with 16MB frame buffer - ZLXp-E2
Important notes
- PBXGA graphics console cannot be used as the system console. Use OPA0 for this purpose.
- If PBXGA graphics card is going to be used, the resolution of CHARON host screen must be sufficient to provide ability to display the graphics console properly.
- If PBXGA graphics card is configured, starting with version 4.12, Charon can now run as a service and is therefore compatible with the Linux Toolkit. Alternatively the emulator can also be run in detached mode (
# <emulator exe> -d <configuration file>
) - If the window of the PBXGA graphics card console is closed by user or killed as a process, it will not re-appear automatically ( the Charon emulator will continue to work). In this situation the user has to restart the pbxga_tv program with the correct parameters, as defined in the configuration file, to restart the graphical display (see PBXGA graphics card#application chapter further)
Virtual PBXGA PCI graphics card settings
Loading virtual PBXGA graphics card
Syntax for loading PBXGA graphics card:
|
Syntax for loading PBXGA graphics card on AlphaServer 400:
|
Example (more examples below):
load PBXGA_BA GYA |
On Charon startup a window will appear on CHARON host monitor to display graphics.
All the parameters described in the "Placement of peripheral devices on PCI bus" chapter, such as "bus", "device", "function", "irq", "irq_bus" are applicable for PBXGA graphics card.
Configuration parameters
size
Parameter | size |
---|---|
Type | Text string |
Value | Predefine the screen size. Possible values: 640x480, 800x600 (default), 1024x768, 1152x900, 1280x1024, 1920x1080 Example:
|
cpu_draw
Parameter | cpu_draw |
---|---|
Type | boolean |
Value | Offloading raster operations. The default value is "true" Example:
|
.
application
Parameter | application |
---|---|
Type | Text string |
Value | Specifies the application to open for displaying the emulated graphics device. The pbxga_tv executable file is provided for this. It is located in the same folder as the Charon emulator executable file. Syntax:
When several graphics cards are loaded, the <device name(s)> have to be separated by a pipe character and the application has to be defined for the latest loaded PBXGA card. See examples below. Note that correct consolidation is only possible when screens are of the same depth and size. Example:
There is no need to supply display size to PBXGA_TV application. Using PanoramiX/XINERAMA extensions to DECwindows is also possible (topics of proper configuration OpenVMS/Tru64 are not covered here). These extensions allow to join multiple heads in one big virtual screen. The PBXGA_TV virtual display unit has special notation allowing to consolidate multiple frame buffers in single window (topology is flexible, to some extent):
Example:
|
Using PBXGA_TV
General Information
The PBXGA_TV display unit starts in passive mode. It displays content of frame buffer but does not react on keyboard input and/or mouse movements. In order to switch it to active mode, place mouse cursor with the window and click once. When PBXGA_TV is active, mouse cursor is stuck to PBXGA_TV window. Press CTRL+ALT+R to release.
The PBXGA_TV display unit starts in Window Mode. Use CTRL+ALT+F to toggle Full Screen Mode.
The PBXGA_TV application uses the SDL2 library to draw its window. The PBXGA_TV driver is statically linked with SDL2. You may need to install the "libdecor" package additionally.
Running PBXGA_TV remotely is not supported.
Please note: PBXGA_TV can only consolidate multiple screens from a single emulator instance.
Command-Line Parameters
The "pbxga_tv" application accepts the following parameters:
Parameter | Description |
---|---|
| Specify the configuration-name in the emulator configuration file |
| Specify the device-name in the emulator configuration file |
--guest-os <GUEST> -Tru64 -OpenVMS | Specify guest operating-system running in emulator. Values for |
-u, --screen-update-period-ms <PERIOD> | Screen update period in milliseconds. If omitted, the default is 100 |
Multiple Screens
The PBXGA_TV application supports using multiple PBXGA adapters in screen consolidation mode, provided that guest OS is configured for PANORAMIX/XINERAMA extension. In order to join multiple PBXGA displays in a single window the value of device-name must list the desired device names as follows:
set session configuration_name = DUAL
...
load PBXGA GYA
load PBXGA GYB
set GYA application = "pbxga_tv -c DUAL -n GYA|GYB"
set GYA application = "pbxga_tv -c DUAL -n GYA/GYB"
Examples
Example 1: 8-bpp graphics on AlphaServer 400
... |
Example 2: 24-bpp graphics on AlphaServer DS20
... |
Example 3: two display units, running independently
... load PBXGA_BA GYA set GYA application = "pbxga_tv -c MYCONF -n GYA" load PBXGA_BA GYB size = 1280x1024 set GYB application = "pbxga_tv -c MYCONF -n GYB" |
In the above example, display units have different resolutions.
Example 4: dual head display, 2x 1280x1024
... |
Example 5: triple head display, 3x 1280x1024
... |
Example 6: Two screens consolidated in a column in one window
... load PBXGA_BA GYAsize = 1280x1024 load PBXGA_BA GYB size = 1280x1024 set GYB application = "pbxga_tv -c MYCONF -n GYA/GYB" |
© Stromasys, 1999-2024 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.
On Linux, PBXGA_TV applications is statically linked with SDL2 library, so no need to install any SDL2 packages. But it might be necessary to install packages SDL2 depends on. Which??? <tbd…>