Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.forth
Subject: Re: OKAD?
Date: Wed, 14 Sep 2016 01:15:26 -0700
Organization: A noiseless patient Spider
Lines: 8
Message-ID: <87bmzqew2p.fsf@jester.gateway.pace.com>
References: <6b82df58-8ef8-4280-b783-ca8729155422@googlegroups.com> <bc52bcf1-4045-425b-bbc4-a0cb0791e2e8@googlegroups.com> <a6031864-c753-4679-98e0-0f0bc59557f0@googlegroups.com> <nqulrq$f85$1@dont-email.me> <1fe82f27-e99d-4809-901a-49c80650c6dd@googlegroups.com> <nqvbi4$1pv$1@dont-email.me> <87lgz0k8jh.fsf@jester.gateway.pace.com> <679aed09-f763-4072-893b-9421e121a204@googlegroups.com> <8db49be3-e9e5-4247-a4ef-425b11efa623@googlegroups.com> <87lgywg6mb.fsf@jester.gateway.pace.com> <20160913000101.46c106d8@HP-6550b> <nr9i18$dus$2@dont-email.me> <20160914085017.6648817c@HP-6550b>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="590ea01354cf4bcbcd857d7ebbd88128"; logging-data="32117"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/p0nopiFk58LQoEp9Wi9ZP"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:fduzAs+/DdcBUwO5ovGWXaV8fT8= sha1:kszjWoYr79sd22GY5P8mlojwKcg=
Xref: csiph.com comp.lang.forth:50961

Jan Coombs <jenfhaomndgfwutc@murmic.plus.com> writes:
> Probably this is what was done in the S40C18. What interested
> me is where the asynchronous boundaries are.  They could be
> just around each processor, or maybe the processor logic is
> further divided into asynchronous sections. 
> Hence my question above, "So what is it?"

I believe each core is clocked by a ring oscillator local to that core.