From 67cbf2f018d38c8fb5641cb7f4ae3a1ab1aaadaa Mon Sep 17 00:00:00 2001 From: Angelo Salese Date: Mon, 24 Nov 2014 02:11:33 +0100 Subject: After-thoughts, (nw) --- src/mame/drivers/dec0.c | 3 ++- src/mame/drivers/taitojc.c | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) (limited to 'src') diff --git a/src/mame/drivers/dec0.c b/src/mame/drivers/dec0.c index 08bd6349eb4..7c0cb65366c 100644 --- a/src/mame/drivers/dec0.c +++ b/src/mame/drivers/dec0.c @@ -1256,7 +1256,8 @@ WRITE_LINE_MEMBER(dec0_state::sound_irq2) /******************************************************************************/ -/* TODO: These are raw guesses, only to get ~57,41 Hz */ +/* This is guesswork, in order to get ~57,41 Hz. + * If real Pixel Clock isn't 5 MHz then htotal/vtotal is different too ... */ #define DEC0_PIXEL_CLOCK XTAL_20MHz/4 #define DEC0_HTOTAL 320 #define DEC0_HBEND 0 diff --git a/src/mame/drivers/taitojc.c b/src/mame/drivers/taitojc.c index bccd5a13a01..7a3e678c72e 100644 --- a/src/mame/drivers/taitojc.c +++ b/src/mame/drivers/taitojc.c @@ -436,7 +436,7 @@ static const int dendego_pressure_table[0x100] = // VSync - 55.6795Hz // HSync - 24.639kHz / 24.690kHz (may be inaccurate) -// TODO: interlacing (hence the different HSync values) +// TODO: why different HSyncs? 24 kHz assumes medium res monitor, so it can't be interlacing. #define HTOTAL (812) #define HBEND (0) #define HBSTART (512) -- cgit v1.2.3