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

gx: use correct constant name for PASSCLR operation #176

Merged
merged 1 commit into from
Jun 23, 2024

Conversation

mardy
Copy link
Contributor

@mardy mardy commented Jun 23, 2024

In the alpha input we should use only GX_CA_* registers. Both GX_CC_A2 and GX_CA_ZERO evaluate to 7, so this is just a cosmetic issue.

The existing error is probably the result of a misunderstanding during reverse engineering.

In the alpha input we should use only GX_CA_* registers.  Both GX_CC_A2
and GX_CA_ZERO evaluate to 7, so this is just a cosmetic issue.

The existing error is probably the result of a misunderstanding during
reverse engineering.
@DacoTaco DacoTaco merged commit 0d23455 into devkitPro:master Jun 23, 2024
1 check passed
Extrems pushed a commit to emukidid/libogc that referenced this pull request Jun 23, 2024
In the alpha input we should use only GX_CA_* registers.  Both GX_CC_A2
and GX_CA_ZERO evaluate to 7, so this is just a cosmetic issue.

The existing error is probably the result of a misunderstanding during
reverse engineering.
Extrems pushed a commit to extremscorner/libogc-rice that referenced this pull request Jun 23, 2024
In the alpha input we should use only GX_CA_* registers.  Both GX_CC_A2
and GX_CA_ZERO evaluate to 7, so this is just a cosmetic issue.

The existing error is probably the result of a misunderstanding during
reverse engineering.
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.

2 participants