Skip to content

Fix the 0/1 values of VDMA_LEN_YES/NO, now VDMA_LEN_ACTIVE/INACTIVE - #94

Merged
Rangi42 merged 2 commits into
gbdev:masterfrom
Rangi42:fix-vdma-len
Aug 28, 2026
Merged

Fix the 0/1 values of VDMA_LEN_YES/NO, now VDMA_LEN_ACTIVE/INACTIVE#94
Rangi42 merged 2 commits into
gbdev:masterfrom
Rangi42:fix-vdma-len

Conversation

@Rangi42

@Rangi42 Rangi42 commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

Fixes #80, though I'm also looking into the other points brought up in its comments.

@Rangi42
Rangi42 requested a review from avivace August 28, 2026 01:48
This avoids confusion over unmarked Boolean values, and allows
their old (mistaken) names to be supported by hardware_compat.inc.
@Rangi42 Rangi42 changed the title Fix the 0/1 values of VDMA_LEN_YES/NO Fix the 0/1 values of VDMA_LEN_YES/NO, now VDMA_LEN_ACTIVE/INACTIVE Aug 28, 2026
@Rangi42

Rangi42 commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator Author

Thanks to @pinobatch for noticing this. The mistake stems from when "VDMA_*" register aliases were added in v4.10.0 (#50).

@ISSOtm ISSOtm left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

lol, silly one

@Rangi42
Rangi42 merged commit 5c5960d into gbdev:master Aug 28, 2026
2 checks passed
@Rangi42
Rangi42 deleted the fix-vdma-len branch August 28, 2026 13:14
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.

FF55 (rHDMA5) contradicts Pan Docs

3 participants