|R4||Bits 0-23: Reason Code|
|Bits 24-31: Driver number|
|Other registers dependant on call|
This vector is used by the RISC OS 5 kernel to communicate with the video driver.
User software should always aim to use the appropriate OS SWI instead of calling GraphicsV directly. The information presented here is mainly of use to OS maintainers and video driver developers.
R4 is used by all GraphicsV calls to store both the reason code and to indicate whether the call has been claimed (i.e. acted upon by a driver). When a driver claims a call it will set R4 to zero. By checking R4 after calling GraphicsV it is possible to determine whether the driver supports that call or not.
|0||Null reason code for when vector has been claimed|
|1||VSync interrupt occurred|
|10||Write palette entry|
|11||Write palette entries|
|12||Read palette entry|
|16||Select startup mode|
|17||List pixel formats|
GraphicsV based video drivers should perform the following sequence of events on startup:
Once OS_ScreenMode 65 is called the driver should expect to start receiving GraphicsV calls from the OS and from other software. Before that point no calls should be received, and if they are then it’s a bug in someone else’s code and not yours.
On shutdown drivers should use the following sequence:
See also HAL Video API for details on how the OS translates GraphicsV calls to HAL calls for systems which contain a video driver in their HAL.