daveb@rtech.UUCP (Dave Brower) (05/21/85)
> There is much talk about the Z800. I thought that I'd inject some > facts straight from Zilog to substanciate the excitement... Reality check: WHO CARES! (Sorry Zilog :-) With the possible exception of small volume embedded controllers, designers are unlikely to select one of these chips. CP/M is a fading memory; who is going to rush to write a compiler for the Z800? Why would anyone select a Z8-bizillion when 68ks and 32ks (even 286s) are out there in reasonable volume now, with software support? Lest you accuse me of bias, I spent > year working on a Z8000 OS destined for ROM. Decent chip, but a loser. Too Bad. [this must be my opinion, i'm even writing it from home.] -- {amdahl|dual|sun|zehntel}\ | Amusing quotation: {ucbvax|decvax}!mtxinu---->!rtech!daveb | (To be supplied in a later ihnp4!{phoenix|amdahl}___/ | revision of the signature.)
agjenkin@kcl-cs.UUCP (Alun Jenkins) (05/25/85)
Ha!! If you had even bothered to read the Zilog spec for the Z80k you would see that the 68000 looks like a mere toy in comparison. Does the 68k have an on chip MMU variable size segments, cache that run at 25MHz , possible contiguous memory of 2^32 bytes. 32032 comes close but cant process as fast. As for instruction sets, so the Z80k has a weird instruction layout but what an instruction set. Basic spec looks something like this...... Features 1. 32 Bit architecture 2. many data types (bit, bit field, logical, signed int ,string ! etc..... 3. Z8000 binary compatible. All internal data paths are full 32 bit implementations. The chip directly supports multiprocessing with memory interlocking. The MMU supports full memory protection. Anyway less of the technical drivel and on to the instruction set. Just a few examples (6502 programmers just drool quietly in the corner). CHK compare destination and source bounds and if out of bound then trap INDEX calculate array index: check scale and accumulate ENTER enter procedure. + EXIT procedure CPSDR compare string decrement & repeat If this chip does not succeed in a big way then the whole business sucks! Send flames to...................................................................... Alun Jenkins ...ukc!kcl-cs!agjenkin
yrdbrd@bmcg.UUCP (Larry J. Huntley) (05/30/85)
In article <413@rtech.UUCP> daveb@rtech.UUCP (Dave Brower) writes: > .................. CP/M is a fading memory; ........ Uh oh. I'd hate to be Dave's local fire engine company. That's right folks, IT'S FIRE-BOMB TIME! (Watch this space) -- Larry J. Huntley Burroughs -(B)- Corporation Advanced Systems Group MS-703 10850 Via Frontera San Diego, CA 92128 (619) 485-4544 -*- "Dear Friends, It's 'ORGAN LEROY' at his organ again." -*-
henry@utzoo.UUCP (Henry Spencer) (06/02/85)
Alun, you forgot one key item of specs: delivery date. Zilog has been
making big promises about the Z8000000000 for a long, long time now.
--
Henry Spencer @ U of Toronto Zoology
{allegra,ihnp4,linus,decvax}!utzoo!henrynather@utastro.UUCP (Ed Nather) (06/03/85)
> Alun, you forgot one key item of specs: delivery date. Zilog has been > making big promises about the Z8000000000 for a long, long time now. > -- > Henry Spencer @ U of Toronto Zoology > {allegra,ihnp4,linus,decvax}!utzoo!henry For every year they slip, they add another zero to the name. :-) -- Ed Nather Astronony Dept, U of Texas @ Austin {allegra,ihnp4}!{noao,ut-sally}!utastro!nather nather%utastro.UTEXAS@ut-sally.ARPA
dgary@ecsvax.UUCP (D Gary Grady) (06/03/85)
> yrdbrd@bmcg.UUCP (Larry J. Huntley) notes: > In article <413@rtech.UUCP> daveb@rtech.UUCP (Dave Brower) writes: > > > .................. CP/M is a fading memory; ........ > > Uh oh. I'd hate to be Dave's local fire engine company. That's right > folks, IT'S FIRE-BOMB TIME! Yep. Well, folks, what do you say? Is it time to create net.flames.wanted? -- D Gary Grady Duke U Comp Center, Durham, NC 27706 (919) 684-3695 USENET: {seismo,decvax,ihnp4,akgua,etc.}!mcnc!ecsvax!dgary
mike@peregrine.UUCP (Mike Wexler) (06/06/85)
> > Ha!! > > If you had even bothered to read the Zilog spec for the Z80k you would > see that the 68000 looks like a mere toy in comparison. > Does the 68k have an on chip MMU variable size segments, cache that run at 25MHz > Anyway less of the technical drivel and on to the instruction set. > > Just a few examples (6502 programmers just drool quietly in the corner). > > CHK compare destination and source bounds and if out of bound then trap > > INDEX calculate array index: check scale and accumulate > > ENTER enter procedure. + EXIT procedure > > CPSDR compare string decrement & repeat > > If this chip does not succeed in a big way then the whole business sucks! > Oh well! So much for RISC. Bye the way you can get 68020's, and 32032's. Where can I get a Z80000?