Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.m68k
Subject: Re: Is 68000 E signal a good clock ?
Message-ID: <13846@cbmvax.commodore.com>
Date: 16 Aug 90 20:27:37 GMT
References: <24775@boulder.Colorado.EDU>
Reply-To: daveh@cbmvax (Dave Haynie)
Distribution: usa
Organization: Commodore, West Chester, PA
Lines: 17

In article <24775@boulder.Colorado.EDU> rainer@hibachi.colorado.edu (Rainer Malzbender) writes:

>Having fortunately avoided 6800 peripherals and micros so far, I know little
>about this signal. Is [the E clock] in fact just the CPU clock divided down, 
>or does it do squirrely things when wait states or interrupts happen ? I need
>it to be rock solid.

The E clock is indeed a free running clock, 4 CPU clocks high, 6 CPU clocks
low.  It's not affected by wait stated, interrupts, or bus arbitration.

>Rainer M. Malzbender                          Technology recapitulates biology.


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
      Get that coffee outta my face, put a Margarita in its place!