Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add feature flag 0x300 for tile engine #276

Merged
merged 1 commit into from
Jan 18, 2025
Merged

add feature flag 0x300 for tile engine #276

merged 1 commit into from
Jan 18, 2025

Conversation

stevesims
Copy link
Contributor

VDU 23,0,&C2,n now checks whether the “tile engine” feature flag has been set before processing the command

this will allow us to release the tile engine whilst the API is still in a state of potential flux

`VDU 23,0,&C2,n` now checks whether the “tile engine” feature flag has been set before processing the command

this will allow us to release the tile engine whilst the API is still in a state of potential flux
@@ -10,7 +10,8 @@
// #include "vdu_layers.h"
// in vdu_sys.h and is called by VDUStreamProcessor::vdu_sys_video()

#define VDP_LAYERS 0xC2 // VDU 23,0,194
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this has been moved into agon.h to the block of code where all the other VDU 23,0 command numbers are defined

@@ -395,6 +396,7 @@
#define TESTFLAG_AFFINE_TRANSFORM 1 // Affine transform test flag

#define FEATUREFLAG_FULL_DUPLEX 0x0101 // Full duplex UART comms flag
#define FEATUREFLAG_TILE_ENGINE 0x0300 // Tile engine flag (layers commands)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the choice of flag number here is slightly arbitrary, as there is not yet a standard for test/feature flag numbering - mostly because we have to few currently defined

here is a very rough proposal for a numbering standard:

high-byte prefix meaning
00 Buffered command extension settings / experimental test flags
01 Communications system settings/configuration
02 VDU system settings and configuration (see #265 )
03 Graphics system extension settings (such as tile engine/layers)

there's a draft PR #267 that currently uses 02xx numbered flags for some VDP protocol settings - those will be renumbered to use 01xx numbering.

@stevesims stevesims merged commit c1b41ca into main Jan 18, 2025
6 checks passed
@stevesims stevesims deleted the tile-engine-flag branch January 18, 2025 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant