Lisp Badge (2021)
The original Lisp badge (or rather, SCHEME badge):<p>Design of LISP-Based Processors
or, SCHEME: A Dielectric LISP
or, Finite Memories Considered Harmful
or, LAMBDA: The Ultimate Opcode,
by Guy Lewis Steele Jr. and Gerald Jay Sussman,
(about their hardware project for Lynn Conway&#x27;s groundbreaking 1978 MIT VLSI System Design Course) (1979) [pdf] (dspace.mit.edu)<p><a href="http:&#x2F;&#x2F;dspace.mit.edu&#x2F;bitstream&#x2F;handle&#x2F;1721.1&#x2F;5731&#x2F;AIM-514.pdf" rel="nofollow">http:&#x2F;&#x2F;dspace.mit.edu&#x2F;bitstream&#x2F;handle&#x2F;1721.1&#x2F;5731&#x2F;AIM-514.p...</a><p>HN discussion (excerpted with updated archive.org links):<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=8859918" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=8859918</a><p>gavinpc quoted Alan Kay from this video:<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=8860680" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=8860680</a><p>gavinpc on Jan 9, 2015 | next [–]<p>Here is Alan Kay from a talk that was just on HN today.<p><a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ubaX1Smg6pY&amp;t=8m9s" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ubaX1Smg6pY&amp;t=8m9s</a><p><pre><code>    The amount of complication can be hundreds of times more than the
    complexity, maybe thousands of times more.  This is why appealing to
    personal computing is, I think, a good ploy in a talk like this because
    surely we don&#x27;t think there&#x27;s 120 million lines of code—of *content* in
    Microsoft&#x27;s Windows — surely not — or in Microsoft Office.  It&#x27;s just
    incomprehensible.
    
    And just speaking from the perspective of Xerox Parc where we had to do this
    the first time with a much smaller group — and, it&#x27;s true there&#x27;s more stuff
    today — but back then, we were able to do the operating system, the
    programming language, the application, and the user interface in about ten
    thousand lines of code.
    
    Now, it&#x27;s true that we were able to build our own computers.  That makes a
    huge difference, because we didn&#x27;t have to do the kind of optimization that
    people do today because we&#x27;ve got things back-asswards today.  We let Intel
    make processors that may or may not be good for anything, and then the
    programmer&#x27;s job is to make Intel look good by making code that will
    actually somehow run on it.  And if you think about that, it couldn&#x27;t be
    stupider.  It&#x27;s completely backwards.  What you really want to do is to
    define your software system *first* — define it in the way that makes it the
    most runnable, most comprehensible — and then you want be able to build
    whatever hardware is needed, and build it in a timely fashion to run that
    software.

    And of course that&#x27;s possible today with FPGA&#x27;s; it was possible in the 70&#x27;s
    at Xerox Parc with microcode.  The problem in between is, when we were doing
    this stuff at Parc, we went to Intel and Motorola and pleading with them to
    put forms of microcode into the chips to allow customization and function
    for the different kinds of languages that were going to have to run on the
    chips, and they said, What do you mean?  What are you talking about?
    Because it never occurred to them.  It still hasn&#x27;t.
</code></pre>
<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=8860722" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=8860722</a><p>DonHopkins on Jan 9, 2015 | prev | next [–]<p>I believe this is about the Lisp Microprocessor that Guy Steele created in Lynn Conway&#x27;s groundbreaking 1978 MIT VLSI System Design Course:<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;MIT78&#x2F;MIT78.html" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>My friend David Levitt is crouching down in this class photo so his big 1978 hair doesn&#x27;t block Guy Steele&#x27;s face:<p>The class photo is in two parts, left and right:<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;MIT78&#x2F;Class2s.jpg" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;MIT78&#x2F;Class3s.jpg" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>Here are hires images of the two halves of the chip the class made:<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;InstGuide&#x2F;MIT78chip photo-1 L.jpg" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;InstGuide&#x2F;MIT78chip photo-2 L.jpg" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>The Great Quux&#x27;s Lisp Microprocessor is the big one on the left of the second image, and you can see his name &quot;(C) 1978 GUY L STEELE JR&quot; if you zoom in. David&#x27;s project is in the lower right corner of the first image, and you can see his name &quot;LEVITT&quot; if you zoom way in.<p>Here is a photo of a chalkboard with status of the various projects:<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;MIT78&#x2F;Status Em.jpg" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>The final sanity check before maskmaking: A wall-sized overall check plot made at Xerox PARC from Arpanet-transmitted design files, showing the student design projects merged into multiproject chip set.<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;MIT78&#x2F;Checkplot s.jpg" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>One of the wafers just off the HP fab line containing the MIT&#x27;78 VLSI design projects: Wafers were then diced into chips, and the chips packaged and wire bonded to specific projects, which were then tested back at M.I.T.<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;MIT78&#x2F;Wafer s.jpg" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>Design of a LISP-based microprocessor<p><a href="http:&#x2F;&#x2F;dl.acm.org&#x2F;citation.cfm?id=359031" rel="nofollow">http:&#x2F;&#x2F;dl.acm.org&#x2F;citation.cfm?id=359031</a><p>ftp:&#x2F;&#x2F;publications.ai.mit.edu&#x2F;ai-publications&#x2F;pdf&#x2F;AIM-514.pdf<p>Page 22 has a map of the processor layout:<p><a href="http:&#x2F;&#x2F;i.imgur.com&#x2F;zwaJMQC.jpg" rel="nofollow">http:&#x2F;&#x2F;i.imgur.com&#x2F;zwaJMQC.jpg</a><p>We present a design for a class of computers whose “instruction sets” are based on LISP. LISP, like traditional stored-program machine languages and unlike most high-level languages, conceptually stores programs and data in the same way and explicitly allows programs to be manipulated as data, and so is a suitable basis for a stored-program computer architecture. LISP differs from traditional machine languages in that the program&#x2F;data storage is conceptually an unordered set of linked record structures of various sizes, rather than an ordered, indexable vector of integers or bit fields of fixed size. An instruction set can be designed for programs expressed as trees of record structures. A processor can interpret these program trees in a recursive fashion and provide automatic storage management for the record structures. We discuss a small-scale prototype VLSI microprocessor which has been designed and fabricated, containing a sufficiently complete instruction interpreter to execute small programs and a rudimentary storage allocator.<p>Here&#x27;s a map of the projects on that chip, and a list of the people who made them and what they did:<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;MIT78&#x2F;MPC78map.gif" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>1. Sandra Azoury, N. Lynn Bowen Jorge Rubenstein: Charge flow transistors (moisture sensors) integrated into digital subsystem for testing.<p>2. Andy Boughton, J. Dean Brock, Randy Bryant, Clement Leung: Serial data manipulator subsystem for searching and sorting data base operations.<p>3. Jim Cherry: Graphics memory subsystem for mirroring&#x2F;rotating image data.<p>4. Mike Coln: Switched capacitor, serial quantizing D&#x2F;A converter.<p>5. Steve Frank: Writeable PLA project, based on the 3-transistor ram cell.<p>6. Jim Frankel: Data path portion of a bit-slice microprocessor.<p>7. Nelson Goldikener, Scott Westbrook: Electrical test patterns for chip set.<p>8. Tak Hiratsuka: Subsystem for data base operations.<p>9. Siu Ho Lam: Autocorrelator subsystem.<p>10. Dave Levitt: Synchronously timed FIFO.<p>11. Craig Olson: Bus interface for 7-segment display data.<p>12. Dave Otten: Bus interfaceable real time clock&#x2F;calendar.<p>13. Ernesto Perea: 4-Bit slice microprogram sequencer.<p>14. Gerald Roylance: LRU virtual memory paging subsystem.<p>15. Dave Shaver Multi-function smart memory.<p>16. Alan Snyder Associative memory.<p>17. Guy Steele: LISP microprocessor (LISP expression evaluator and associated memory manager; operates directly on LISP expressions stored in memory).<p>18. Richard Stern: Finite impulse response digital filter.<p>19. Runchan Yang: Armstrong type bubble sorting memory.<p>The following projects were completed but not quite in time for inclusion in the project set:<p>20. Sandra Azoury, N. Lynn Bowen, Jorge Rubenstein: In addition to project 1 above, this team completed a CRT controller project.<p>21. Martin Fraeman: Programmable interval clock.<p>22. Bob Baldwin: LCS net nametable project.<p>23. Moshe Bain: Programmable word generator.<p>24. Rae McLellan: Chaos net address matcher.<p>25. Robert Reynolds: Digital Subsystem to be used with project 4.<p>Also, Jim Clark (SGI, Netscape) was one of Lynn Conway&#x27;s students, and she taught him how to make his first prototype &quot;Geometry Engine&quot;!<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;MPCAdv&#x2F;MPCAdv.html" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>Just 29 days after the design deadline time at the end of the courses, packaged custom wire-bonded chips were shipped back to all the MPC79 designers. Many of these worked as planned, and the overall activity was a great success. I&#x27;ll now project photos of several interesting MPC79 projects. First is one of the multiproject chips produced by students and faculty researchers at Stanford University (Fig. 5). Among these is the first prototype of the &quot;Geometry Engine&quot;, a high performance computer graphics image-generation system, designed by Jim Clark. That project has since evolved into a very interesting architectural exploration and development project.[9]<p>Figure 5. Photo of MPC79 Die-Type BK (containing projects from Stanford University):<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;MPCAdv&#x2F;SU-BK1.jpg" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>[...]<p>The text itself passed through drafts, became a manuscript, went on to become a published text. Design environments evolved from primitive CIF editors and CIF plotting software on to include all sorts of advanced symbolic layout generators and analysis aids. Some new architectural paradigms have begun to similarly evolve. An example is the series of designs produced by the OM project here at Caltech. At MIT there has been the work on evolving the LISP microprocessors [3,10]. At Stanford, Jim Clark&#x27;s prototype geometry engine, done as a project for MPC79, has gone on to become the basis of a very powerful graphics processing system architecture [9], involving a later iteration of his prototype plus new work by Marc Hannah on an image memory processor [20].<p>[...]<p>For example, the early circuit extractor work done by Clark Baker [16] at MIT became very widely known because Clark made access to the program available to a number of people in the network community. From Clark&#x27;s viewpoint, this further tested the program and validated the concepts involved. But Clark&#x27;s use of the network made many, many people aware of what the concept was about. The extractor proved so useful that knowledge about it propagated very rapidly through the community. (Another factor may have been the clever and often bizarre error-messages that Clark&#x27;s program generated when it found an error in a user&#x27;s design!)<p>9. J. Clark, &quot;A VLSI Geometry Processor for Graphics&quot;, Computer, Vol. 13, No. 7, July, 1980.<p>[...]<p>The above is all from Lynn Conway&#x27;s fascinating web site, which includes her great book &quot;VLSI Reminiscence&quot; available for free:<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>These photos look very beautiful to me, and it&#x27;s interesting to scroll around the hires image of the Quux&#x27;s Lisp Microprocessor while looking at the map from page 22 that I linked to above. There really isn&#x27;t that much too it, so even though it&#x27;s the biggest one, it really isn&#x27;t all that complicated, so I&#x27;d say that &quot;SIMPLE&quot; graffiti is not totally inappropriate. (It&#x27;s microcoded, and you can actually see the rough but semi-regular &quot;texture&quot; of the code!)<p>This paper has lots more beautiful Vintage VLSI Porn, if you&#x27;re into that kind of stuff like I am:<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;MPC79&#x2F;Photos&#x2F;PDFs&#x2F;MPC79ChipPhotos.pdf" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p>A full color hires image of the chip including James Clark&#x27;s Geometry Engine is on page 23, model &quot;MPC79BK&quot;, upside down in the upper right corner, &quot;Geometry Engine (C) 1979 James Clark&quot;, with a close-up &quot;centerfold spread&quot; on page 27.<p>Is the &quot;document chip&quot; on page 20, model &quot;MPC79AH&quot;, a hardware implementation of Literate Programming?<p>If somebody catches you looking at page 27, you can quickly flip to page 20, and tell them that you only look at Vintage VLSI Porn Magazines for the articles!<p>There is quite literally a Playboy Bunny logo on page 21, model &quot;MPC79B1&quot;, so who knows what else you might find in there by zooming in and scrolling around stuff like the &quot;infamous buffalo chip&quot;?<p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;VLSIarchive.html" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a><p><a href="https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.umich.edu&#x2F;people&#x2F;conway&#x2F;VLSI&#x2F;VLSI.archive.spreadsheet.htm" rel="nofollow">https:&#x2F;&#x2F;web.archive.org&#x2F;web&#x2F;20210131033223&#x2F;http:&#x2F;&#x2F;ai.eecs.um...</a>