| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
|
| |
|
|
| |
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
These are quite mindless, but they are rather useful on simple examples
in which we don't care about performance and we just want to show
something on the screen.
For now this didn't matter much, but on real hardware I was able to
reproduce the same glitches as with emulators which randomized memory on
both the CPU memory and on the PPU. Hence, just allow some examples to
manually reset these regions and avoid silly graphical glitches.
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
|
| |
|
|
| |
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
|
| |
|
|
| |
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
First of all, move some reading utilities into the new `shared`
directory, so controllers can be read by more than one example. Second,
even if we keep the example on `basics/input.s` simple, let's provide a
safe alternative for the other examples.
Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
|
|
|
Add an example on how to flicker sprites so to not surpass the scanline
limit for them.
Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
|