ctx,st3m: increment the frame-clock of the texture cache context

All the contexts share the texture and eid handling of the "master" ctx context, which is within the rasterizer of the rendering context for framebuffer 0. For the age-tracking to work right we need to have a logical clock tied to the use of textures, this adds a small convenience function to the ctx implementation to inject an appropriate increment of this clock per rendered frame. This makes the ejection policy of discarding a least frequently used eid, which works well with eids created on demand and cached by an identity.

added 1 commit

• fba7fe7a - ctx: enable CTX_FORMAT_RGB8 needed for jpg

Compare with previous version

added 3 commits

• f8f80b52 - ctx: set number of concurrent textures to 32
• a024c3bd - ctx: sync with upstream to get public ctx_set_frameclock
• 047feef4 - st3m_gfx: increment master context frameclock for eid expiry

Compare with previous version

resolved all threads

resolved all threads

added 2 commits

• 7ca783fc - ctx: sync with upstream to get public ctx_set_frameclock
• 3fdba439 - st3m_gfx: increment master context frameclock for eid expiry

Compare with previous version

added 4 commits

• b80cbb09 - 1 commit from branch main
• b2d9194f - ctx: set number of concurrent textures to 32
• b947517a - ctx: sync with upstream to get public ctx_set_frameclock
• 6e2ba5a4 - st3m_gfx: increment master context frameclock for eid expiry

Compare with previous version

added 4 commits

• 43ac0833 - 1 commit from branch main
• b4edc49c - ctx: set number of concurrent textures to 32
• bff400f1 - ctx: sync with upstream to get public ctx_set_frameclock
• b396246e - st3m_gfx: increment master context frameclock for eid expiry

Compare with previous version

merged