1994-01-26 - Re: clipper pin-compatible chip

Header Data

From: m5@vail.tivoli.com (Mike McNally)
To: koontzd@lrcs.loral.com (David Koontz )
Message Hash: 97315ba7e5f88eed59e789aae281b696b9fa6755fc180ff2e86f4e9b48925f97
Message ID: <9401261926.AA06623@vail.tivoli.com>
Reply To: <9401261919.AA22973@io.lrcs.loral.com>
UTC Datetime: 1994-01-26 19:27:12 UTC
Raw Date: Wed, 26 Jan 94 11:27:12 PST

Raw message

From: m5@vail.tivoli.com (Mike McNally)
Date: Wed, 26 Jan 94 11:27:12 PST
To: koontzd@lrcs.loral.com (David Koontz )
Subject: Re: clipper pin-compatible chip
In-Reply-To: <9401261919.AA22973@io.lrcs.loral.com>
Message-ID: <9401261926.AA06623@vail.tivoli.com>
MIME-Version: 1.0
Content-Type: text/plain



David Koontz  writes:
 > While the clipper chip and its CCEP brethern ...

I'm sure you're right; I don't mean to claim knowledge to anythign
like this level of detail.

 > Operating in a system expecting a clipper chip potentially restricts
 > the keyspace.

Indeed.

 > The point being that dropping an IDEA chip in is not 'plug and play'.

I believe this; my point was simply to clarify.  I interpreted Tim's
note as having to do with reverse-engineering Clipper, while the
original note seemed more along the "plug and play" lines.  Now that I
think about it, it's probably the case the Tim didn't misunderstand at
all, but was on a tack about how you'd pretty much have to completely
re-engineer the thing.  Or something.

Seems like it'd be easier to compete with Clipper by simply building
an alternative from the ground up.

--
| GOOD TIME FOR MOVIE - GOING ||| Mike McNally <m5@tivoli.com>       |
| TAKE TWA TO CAIRO.          ||| Tivoli Systems, Austin, TX:        |
|     (actual fortune cookie) ||| "Like A Little Bit of Semi-Heaven" |







Thread