comparison vdp.h @ 1371:5b20840711c1

Remove HINT_FUDGE and make a small adjustment to how VDP syncs with rest of system instead. Worse results on CRAM dot issue, but much less of a hack
author Michael Pavone <pavone@retrodev.com>
date Tue, 23 May 2017 21:09:38 -0700
parents 033dda2d4598
children e587f16e7d3d
comparison
equal deleted inserted replaced
1370:eaca4443e831 1371:5b20840711c1
213 uint8_t *tmp_buf_b; 213 uint8_t *tmp_buf_b;
214 } vdp_context; 214 } vdp_context;
215 215
216 void init_vdp_context(vdp_context * context, uint8_t region_pal); 216 void init_vdp_context(vdp_context * context, uint8_t region_pal);
217 void vdp_free(vdp_context *context); 217 void vdp_free(vdp_context *context);
218 void vdp_run_context_full(vdp_context * context, uint32_t target_cycles);
218 void vdp_run_context(vdp_context * context, uint32_t target_cycles); 219 void vdp_run_context(vdp_context * context, uint32_t target_cycles);
219 //runs from current cycle count to VBLANK for the current mode, returns ending cycle count 220 //runs from current cycle count to VBLANK for the current mode, returns ending cycle count
220 uint32_t vdp_run_to_vblank(vdp_context * context); 221 uint32_t vdp_run_to_vblank(vdp_context * context);
221 //runs until the target cycle is reached or the current DMA operation has completed, whicever comes first 222 //runs until the target cycle is reached or the current DMA operation has completed, whicever comes first
222 void vdp_run_dma_done(vdp_context * context, uint32_t target_cycles); 223 void vdp_run_dma_done(vdp_context * context, uint32_t target_cycles);