Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: who can use a Harris RTX-2000 processor Date: Tue, 11 Apr 2017 21:04:51 -0700 Organization: A noiseless patient Spider Lines: 14 Message-ID: <8737del198.fsf@nightsong.com> References: <87bms2lafo.fsf@nightsong.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="0de1f87b5972fac17e91256555e4d05f"; logging-data="7653"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+FEBqKnu4C3V5IBGUc79Bu" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:177BXDY5N2yIrzztAvoYXLIKsiY= sha1:NGc45aBEwtoT1bo/M4p351FlCSM= Xref: csiph.com comp.lang.forth:57094 rickman writes: > I'm good with VHDL, but I prefer to work from specifications rather > than trying to divine a spec from poor documentation. I'm not clear > on what is available. The RTX-2000 was space qualified if I'm not confusing it with something else, so I'd expect it to be documented out the wazoo. Maybe it's a matter of finding some manuals for it and working from those. If it were me, I'd start with a software emulation. Ymmv. Why is the RTX-2000 interesting anyway? Do people have old code they want to run on it? Do they want to write new code for a stack processor just because it's cool? If the latter, exact compatibility with the RTX-2000 isn't as important. For that matter, there's always the J1.