GraphicsV 13 (changes)

Showing changes from revision #8 to #9: Added | Removed | Changed

GraphicsV

» GraphicsV 13

Graphics Vector (42)

Use

The kernel issues this call to instruct the driver to perform a hardware-accelerated rendering task. The appropriate driver should respond to the call in the following manner:

• If the render operation is supported, perform the requested action and set R4 to 0 to claim the call. If bit 0 of R0 is set, synchronise with the video controller to ensure the operation is complete before returning.
• If the render operation is unsupported, leave the call unclaimed. If bit 1 of R0 is set, synchronise with the video controller to ensure that any previous render operations have completed.
• If no hardware acceleration is supported at all, the driver can safely ignore the call.

Notes

Screen memory will typically be bufferable – GraphicsV driver implementations should make sure to perform the necessary memory barrier operations at the start/end of any given acceleration op (e.g. write barrier at start, read barrier at end). Suitable barrier routines are available via OS_MMUControl 2.

If no driver responds to the request request, then there is no generic software fallback in place. Software rendering fallbacks must be handled on a case-by-case basis by the caller. Therefore Therefore, any user software which wishes to make use of hardware acceleration should either do so via theVDU interface (e.g. use block copy/fill OS_Plot operations, which will have the appropriate fallbacks in place inside the kernel), or call GraphicsV directly and use their own software fallback for any unsupported operations. Just because one call succeeds succeeds, it does not guarantee that the next call will succeed, or that a call made with slightly different parameters will succeed.

See also

• GraphicsV