gbdev / gbdev/pandocs

When exactly can monochrome consoles read from wave RAM?

Open
#590 0 comments 0 reactions 0 assignees View on GitHub
content
Dominant language
Markdown
Stars
783
Forks
134
Avg merge
6h 54m
Merged PRs (30d)
3

Description

I suggest removing the word "only" from:

> On monochrome consoles, wave RAM can only be accessed on the same cycle that CH3 does. Otherwise, reads return $FF, and writes are ignored.

because it sounds like it's saying access is not allowed when CH3 is inactive. Not a big deal, because there is clarification below:

> Wave RAM can be accessed normally even if the DAC is on, as long as the channel is not active.

Or maybe normal access when CH3 is inactive should be mentioned before all 3 bullet points on misbehaving accesses, because it's what most people are going to want to do.

Contributor guide

Open the contributing guide

Research direction

Start with the wave RAM section containing the two quoted passages. Review the wording and ordering around monochrome-console access, then make the explanation clearly distinguish inactive CH3 access from misbehaving accesses. Done means the section no longer implies that access is forbidden whenever CH3 is inactive.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.