Skip to content
This repository has been archived by the owner on Feb 11, 2021. It is now read-only.

Latest commit

 

History

History
109 lines (86 loc) · 4.51 KB

README.QNX

File metadata and controls

109 lines (86 loc) · 4.51 KB
 
May 6, 2004
May 6, 2004
1
README.QNX by Mike Gorchak <mike@malva.ua>, <lestat@i.com.ua>
Jun 10, 2009
Jun 10, 2009
2
Last changed at 10 Jun 2009.
Dec 10, 2003
Dec 10, 2003
3
Jun 10, 2009
Jun 10, 2009
4
5
QNX Photon and GF drivers are being constructed, OpenGL ES support is
finished. Still no 2D renderer support in GF and Photon drivers.
Mar 24, 2009
Mar 24, 2009
6
7
QNX QSA (QNX Sound Architecture) driver is ready.
QNX CDROM driver is ready.
Jun 10, 2009
Jun 10, 2009
8
QNX HID input driver is finished.
Mar 24, 2009
Mar 24, 2009
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
----------------------
-- SDL QSA driver --
----------------------
Due to QNX Sound Architecture limitations software could not determine
what playback channels are designed for, so some casus can be. For example,
output after testmultiaudio test utility execution:
Using audio driver: qsa
playing on device #0: ('Vortex 8820 @ fb000000 d0')...done.
playing on device #1: ('Vortex 8820 @ fb000000 d1')...done.
playing on device #2: ('i8x0 @ d800 d0')...done.
playing on device #3: ('i8x0 @ d800 d1')...done.
playing on all devices...
Open device 3 failed: QSA: snd_pcm_channel_params failed: Invalid argument
If speakers are connected to both audio cards: Vortex 8820 and Intel
Integrated Audio we can hear sound playback on device #0 and devices #2, #3
only. Device #1 is an unknown PCM channel which does not produce any sound.
As for error during device #3 opening, it's caused by QSA software mixer
channel, because it can't open real hardware device #2, since it's already
opened by SDL.
After simultaneous sound playback on all devices utility testmultiaudio
stays running waiting for sound playback finish on device #1, which is
locked up due to some Aureal Vortex 8820 driver limitations.
Mar 17, 2009
Mar 17, 2009
37
38
39
40
41
42
43
44
45
46
47
48
49
---------------------
-- SDL GF driver --
---------------------
Here is an additional information about SDL GF driver:
* 0. Introduction.
* 1. Environment variables which SDL GF driver supports.
* 2. Custom video modes.
* 3. Limitations.
0. Introduction.
Mar 24, 2009
Mar 24, 2009
50
51
52
53
SDL GF driver is a layer between SDL and QNX Graphics Framework (GF).
SDL GF driver also supports OpenGL ES through the QNX Graphics Framework.
Hardware accelerated features which SDL can support depend on real hardware
capabilities.
Mar 17, 2009
Mar 17, 2009
54
55
56
1. Environment variables which GF driver supports.
Mar 24, 2009
Mar 24, 2009
57
58
59
60
61
62
63
64
65
GF driver supports the following environment variables for QNX GF
specific customization options:
a) SDL_VIDEO_GF_REFRESH_RATE - refresh rate of video output in Hz.
Without this environment variable declaration SDL controls refresh
rate of your display. If this enironment variable is set to 0, SDL
will control refresh rate of display, otherwise value of flag
SDL_VIDEO_GF_REFRESH_RATE is used for all screen resolutions as
refresh rate. This example will set 60Hz refresh rate as refresh rate
for all graphics modes:
Mar 17, 2009
Mar 17, 2009
66
67
68
69
70
export SDL_VIDEO_GF_REFRESH_RATE=60
2. Custom video modes.
Mar 24, 2009
Mar 24, 2009
71
72
73
74
75
76
Since most QNX graphics drivers support GENERIC video modes, i.e. you
can specify any horizontal and vertical resolution and any refresh rate,
SDL GF driver uses its own fullscreen modes list, which can be incomplete.
You can add any custom video mode, which your QNX graphics driver supports
by editing file ./src/video/qnxgf/SDL_qnxgf.c. Custom graphics mode
definition looks like this:
Mar 17, 2009
Mar 17, 2009
77
Mar 24, 2009
Mar 24, 2009
78
{0, 1024, 640, 60, NULL}, /* 1024x640 mode is 60Hz only */
Mar 17, 2009
Mar 17, 2009
79
Mar 24, 2009
Mar 24, 2009
80
81
82
83
84
You must specify horizontal resolution as the second parameter, vertical
resolution as the third one and refresh rate as the fourth parameter.
Please leave the first and the last parameters as 0 and NULL. Then send me
your changes to e-mail address which is specified in the header of this
document.
Mar 17, 2009
Mar 17, 2009
85
86
87
88
89
3. Limitations.
There are few limitations while using SDL GF driver:
Mar 24, 2009
Mar 24, 2009
90
91
92
93
94
95
96
97
98
99
a) Since GF driver supports fullscreen modes only, when flag
SDL_WINDOW_FULLSCREEN is not specified, SDL GF driver will try to find the
fullscreen graphics mode which corresponds to SDL window size. Refresh rate
will be the lowest available, if SDL_VIDEO_GF_REFRESH_RATE environment
variable is not set.
b) As confirmed by QSSL none of existing video drivers has support of
doublescan low-resolution video modes. So modes below 640x480 are not
supported. If your video driver supports low-resolution video modes, please
add SDL_GF_LOWRESOLUTION flag to the gf_devicename array in the SDL_qnxgf.c
source file.
Jun 10, 2009
Jun 10, 2009
100
101
c) Since GF framework supports hardware mouse cursor only, you'll get
hardware mouse cursor in case of specific graphics driver supports it.
Mar 24, 2009
Mar 24, 2009
102
103
104
105
106
107
108
109
-------------------------
-- SDL Photon driver --
-------------------------
----------------------------
-- SDL HID input driver --
----------------------------