Wrapping the context is pretty straightforward. This is only complicated by needing to account for the upside-down framebuffer in a few places.
This is done to avoid cluttering vo_gpu_next.c with more ifdeffery and context-specific code when additional backends are added in the near future. Eventually gpu_ctx is intended to take the place of ra_ctx to further separate gpu and gpu_next.