This homework is due at the beginning of class Tuesday, 9/5/2006.

For the wiki question (below), feel free to read over each other's answers. Do not mess with someone else's answers.

Questions

1. Register on this Wiki and add yourself to Fall 2006/StudentList

2. Buy the textbook (see Fall 2006/Course Syllabus)

3. Answer the following questions right here on the wiki (below) and also bring them to class. Do not forget to put down your name.

   1. Why are you taking this class?
   2. What is Computer Architecture? (cite sources if you use any)
   3. What do you look for when you buy a computer?
   4. What is your favorite processor and why?

   5. Name at least three things that you want to learn in this class. Be semi-specific.

Answers

• MarkChang (these are less-than-serious answers -- yours will be more serious)

  1. Because I really dig MarkChang.

  2. Computer Architecture is a required class at Olin College.
  3. How sexy the case is and if it makes lots of noise.

  4. The Intel Pentium Pro. Because it has the word Pro in the name.

  5. How a computer works.
  6. How to use binary numbers.
  7. How to conquer the world.

• BenHayden

  1. I'm taking this class to learn another way of thinking about computation.
  2. Computer Architecture is the design of circuits to perform some sort of computation.
  3. I have never bought my own computer, and I'd have to ask a real ECE what I should look for. If I had to guess, I'd look for lots of big numbers on the specs.

  4. My favorite processor [even though I have not yet had the privilege of using one] is the most recent Symbolics lisp machine because I like lisp.

  5. 1. I want to learn how to think efficiently in verilog.
     2. I want to learn what sorts of things can be done in verilog and hardware.
     3. I want to learn what sorts of things should be done in verilog and hardware, and what sorts of things shouldn't.

• StephenLongfield

  1. I've always wanted to know how computers and digital logic all work, as well as what goes on inside of the black box that is my computer.
  2. Computer Architecture is wireing sequences of simple digital logic elements to do complicated operations.
  3. Typically, when building a computer, I look at a particular video games' recomended specs, and build for that. Also, I look for price. (My last computer was built spec'd for Half Life 2)
  4. My favorite processor is the K6-2. This is mostly for sentimental value, as I used a computer with this processor in it for the majority of high school. This computer was the first computer I upgraded, and swapping this processor in (I got it from a friend) was the first major hardware upgrade I ever made.
  5. 1. I want to learn how to use FPGAs.
     2. I want to learn how computers understand their input, and use it to do complicated tasks (as in, how using only bitshifts, addition, subtraction and etc. I can play Half Life 2).
     3. I want to really understand how computers do less complicated tasks, like addition and multiplication.

• JoeRoskowski

  1. It seems like really cool content and fills in a gap in my knowledge of how computers work.
  2. Computer Architecture is how a computer is orginized; for example how it adresses memory.
  3. Price per needed performance.
  4. The Intel 80386 because it was the first one I remember using by name -- And it ran Oregon Trail.
  5. 1. How adressing memory works.
     2. Synchonization (and Multi-theading)
     3. FPGAs

• JeffDezso

  1. I've always wanted to know how basic binary logic can be used to build a complex computer. That fascination is part of what attracted me to computers/computer engineering.
  2. Computer Architecture is assembling simple logic units into larger computational blocks.
  3. Maximize performance versus cost.
  4. AMD Athlon - because it was in the first computer I built from parts.
  5. 1. How computational elements are built from logic elements.
     2. How a processor controls itself. How does it know what to do when, and how does it prioritize it?
     3. FPGAs

• GeorgeHarris

  1. I've done some computer architecture work with the 68k before, and I'd like to expand upon what I've done and take it much furthur than using a processor to turn some LEDs on. It also seems like a lot of fun.
  2. The design of a logic based system to perform a set of computational tasks.
  3. Whether or not it's a Mac. If it's not, I look at the best part I can get for my money and balance what I need with what I don't.
  4. The Motorola 68k for the above reason.
  5. 1. How to program and use FPGAs
     2. How a GPU works (vertex/shader pipelines and all those other big words they throw around)
     3. How the major architectures work and differ
     4. The internals of a CPU

• JamesWhong

  1. I don't like black boxes. Computers of all types are such a crucial part of everyday life I need to know how they work from the ground up. Plus, it'll make me a better programmer.
  2. Computer architecture is everything between analog/digital logic and computer science.
  3. Is it stable? Is it cheap? Is it fast enough for Starcraft?
  4. The ARM7TDMI. It's a low power processor used in most Nokia mobile phones, the iPod, Gameboy Advance, the Nintendo DS, Mindstorms NXT... I think it's amazing the kind of performance you can get out of these things for their price in power.
  5. 1. How the major architectures (x86, x86_64, ARM*...) work from the gate level, why they're different and how they can be improved.
     2. I want to learn some machine code, not necessarily for any specific processor, I just want to know what level my hardware operates on.
     3. The major shortcomings of today's processors (what can be done better).

• MattDonahoe

  1. I know how transistors work. I know how to program a PIC in assembly. I figure this class is the bridge between those two.
  2. Computer Architecture in its broadest sense would involve building a device that can perform computation.
  3. The computer I build 2 years ago had mostly top of the line parts. If I were to buy a computer again, it would prefer something that was more interesting that just fast.
  4. I read a lot about the Cell Processor, so I guess that's my favorite. I hear that in the PS3, one of the 9 redundant parts of the chip is deactivated at first. That way it can go live if another part of the chip breaks. Interesting thinking.
  5. I want to learn how to go from AND's and OR's etc to operations and computation. I also want to learn about FPGA's and hopefully make some cool programs that utilize them. Lastly I think it would be cool to learn more about parallel computing.

• JeffreyDeCew

  1. It's one of the last and greatest gaps in my knowledge of how Half-Life 2 works.
  2. I thought of computer arcitechture as being the art-form of computer engineering, until Mark in class made it feel more like the on-site construction of a pre-fab house. Now I'm just confused (but still excited).
  3. Price, Function, Reliability, and Compatability.

  4. MY BRAIN!!! It doesn't overheat, I don't worry about the liquid cooling system causing shorts, and although I sacrifice reliability for free-will, I still managed to pass E&M.

  5. I want to learn:
     1. The basics of how switching transistors can create predetermined logic
     2. I want to understand the techniques used to simplify a microchip so that when they start getting big, people can still understand how they work.
     3. I want to learn and understand what the rewards of an asynchronous computer might be over a synchronous one.

• KatKim

  1. Its my last prerequisite before I am an official Olin ECE! I also want to see which is truely better: Analog or Digital!
  2. Computer Architecture has to do with the digital logic that allows computing to happen. Includes processors, registers, buses, and LOTS of transistors!
  3. What I really look for in a computer is a good sense of humor, some charm, and, of course, a hot looking body.
  4. I couldn't name an exact processor, but I like dual or multicore processors because they have lower heat generation and save energy in data centers.
  5. I want to learn:
     1. Why dual and multicore processors have lower heat generation, and how can one design a processor to reduce heat generation?
     2. What configurations of analog circuits make up digital components?
     3. Why do people like FPGAs and verilog so much? (which involves learning to program FPGAs in verilog)
     4. How will IPv6 change processor architecture, if at all? and if not, what will it change about networking?

• AnneItsuno

  1. I am taking this class because it is a requirement for ECE majors, and also because it sounds interesting and applicable to things I would like to do in the future.

  2. Computer architecture is essentially the theory behind the design of a computer. It encompasses the arrangement of computer processing components, their relationships and functionality, and system software. Sources:wordnet.princeton.edu/perl/webwn; en.wikipedia.org/wiki/Computer_architecture. I would simply say, how it involves how a computer is designed and built and what components are used.

  3. I have actually never purchased my own computer before! But if I were to buy a new computer, I would look at storage size, clocking speed, the type of graphics card, and the type of processor. And most importantly, cost! and aesthetics. Hah.
  4. My favorite processor would be the Intel Pentium, because I don't think I've used anything else. Anything functional.
  5. I want to learn:
     1. How FPGAs work and how to program one?
     2. How to become proficient at HDL.
     3. Learn about differents components of the computer.

• MeenakshiVembusubramanian

  1. I'm interested in that whole graduating with a degree thing.
  2. I have exposure to programming as well as fundamental devices; my impression of Comp Arch. is that it involves bringing these two together and understanding how which transistor on which chip knows to do what when I run my Matlab script.
  3. At this point in life, really just the most I can get given a pricetag.
  4. I don't have one.
  5. I want to know enough to have a favourite processor, and just understand how a processor works inside out. Also, I can't wait to find out what exactly is so cool about FPGA's? What are other options in the same class that do things differently? (ie., what would an alternative to using an FPGA be?)

• DucNguyen

  1. I'm taking this class to fulfill my ECE requirements and also to learn how computers work on a system-wide level. The little details in a computer fascinate me. I know how individual transistors/MOSFETs work but I don't know how that translate into a bigger frame where a typical proc has hundreds of millions of transistors. That's not to mention the special duty processing unit like the GPU. It is just cool. Also, the colors on a wafer look kinda cool.
  2. Computer Architecture, I'm guessing, is the framework of how the different components of a computer are made and put together to work seamlessly. There is the processing stuff and then also the data transfer channels. There are different types of connections between the different components of a computer and/or the peripherals.
  3. Depending on the budget and the purpose of the computer, I would look accordingly. Most likely, I would look for the most bang for the buck -- a computer that performs reasonably well for the budget that I have. Also, another major consideration is power consumption vs. performance. AMD's have traditionally done better than Intel in this area but the Cell is pretty cool too. I don't expect to be able to build a system on a Cell though.
  4. My current favorite proc is the Intel Core 2 line, espcially the upper echelon with 4MB of cache. They perform well and overclock well too, much better than the previous generation of the Intel Core Duo. Also, the price looks really good, at least on paper. This lineup has another side effect; it pushed AMD to slash prices on their procs, which is good for all consumers.
  5. 3 things I want to learn in this class:
     1. non-sequential programming, huh? Is it possible?
     2. how to deal with binary and base 2 operations.
     3. parallel computing.

• RobQuimby

  1. I’d like to learn more about how exactly things as complicated as modern software programs can be broken down into something as seemingly simple as gate-level diagrams.
  2. Well, it makes sense that “computer architecture” would be the designing and construction of computers.
  3. Generally, I look for something as cheap as possible that will be able to complete the tasks I need it for, and preferably be reasonably reliable.
  4. I’m going to go with the Mobile Athlon 2500+, because even though I never had one, I always admired it for the period of time in which it was about the most desired CPU for desktops due to its overclockability. It’s always fun when good engineering finds multiple uses.
  5. Stuff I'd like to learn:
     1. I’d like to have a deeper understanding of what exactly computer architecture is. Right now, I’m mostly going from just knowing what the words “computer” and “architecture” mean.
     2. I want to know what the differences are between various architectures, and have a better conception of the differences in processors than “This one has more L2 cache!”
     3. I want to build something cool. I remember seeing a pong project at expo that I believe came out of this class, and I thought that was incredible.

• AnthonyRoldan

  1. I'm taking this class because I'd like to connect an understanding of electronics with an understanding of code and see how the silicon in a computer chip actually translates to it doing things for you.
  2. Computer Architecture is the connection between electronics and computing, and then also the connection between computing and code.
  3. It depends - in a desktop, I usually look for power and graphics ability, whereas in a laptop I look for small size and an appealing look.
  4. I think my favorite processor is the second-generation socket 370 Intel Celeron. It performed better than it was supposed to, beating out the Pentium IIs it was supposed to be worse than at most things. I remember building a dual-celeron rig in 1998 or so that was cheaper than a just-released Pentium III and way, way l33ter.
  5. Things to Learn
     1. I think my first goal in this class is to know enough to be able to build a computer if I were to be thrown back in time to, say, the early 20th century. Or perhaps be able to build one from scratch after the apocalypse.
     2. I'd like to learn about FPGAs and get to use them.
     3. What exactly do people mean when they say "pipeline"? What is a "processor instruction"? Why would a reduced instruction set be to your advantage?

• ChrisStone

  1. I really just want to see if my high school Comp Arch teacher was making everything up. Oh yeah, and it's required.
  2. Computer Architecture is how you use digital logic to perform meaningful tasks.
  3. I read the recommended system reqs on my favorite game at the time and add a little to everything... and then I look at price.
  4. Whichever I last saw in a commercial. To be honest, I don't really have a favorite processor.
  5. Things to Learn
     1. how to use FPGA's
     2. what would make a specific processor my favorite
     3. how to compare different architectures and know what to look for (determine advantages/disadvantages to two different computer architectures).

• OlekLorenc

  1. I'm taking the class because Computer Architecture would be important to understand for efficient systems design.
  2. Computer Architecture is the bridge between cirtcuit design and programming.
  3. When I build a computer I generally look for parts which will create a stable system with good performace per dollar.
  4. I like my PII 450 which I got back when it was top of the line, and has since been faithfully serving as my web/mail server.
  5. Things to Learn
     1. How wires, resistors, capacitors, etc. can do useful things (in terms of logic).
     2. What's inside those colorful, holographic, little boxes called processors.
     3. What a FPGA is, since people talk about them a lot in reference to Computer Architecture.

• ChristopherDellin

  1. Cause I don't think about computers much from that direction.
  2. Computer Architecture is the science of designing the hardware used for computing.
  3. I look for something that:
     1. Doesn't waste my time or money
     2. I can take apart if something breaks or I want to upgrade something
     3. I can put back together
     4. Doesn't come with any software
     5. Has opensource drivers for all the parts
  4. Quantum. Cause it's so new, non-intuitive, and can factor prime numbers really really fast.
  5. I want to learn:
     1. How today's computers accomplish their tasks at a hardware level.
     2. Why there's relatively inefficient about it.
     3. Some cool, crazy stuff about new types of computation (quantum? extremely-low-power?).

• NinaCary

  1. I'm not sure what my major is yet, but I declared as a Systems. I'm taking this class to see if you can convert me to an ECE.
  2. "They'll teach you how to make a computer... work." -JJ
  3. I've never bought a computer off the shelf. I've usually gotten free/cheap ones and salvaged bits and pieces that still worked.
  4. Don't have one.
  5. Teach me this:
     1. Verilog
     2. How to pick a favorite processor
     3. A better definition of computer architecture

• CodyWheeland

  1. I am taking this class for three reasons:
     1. I want to better understand how to design and use processors
     2. It is required for an ECE degree

     3. MarkChang is AWESOME!

  2. Computer architecture is the art of designing the efficient flow of data within a computer or other processing device.
  3. I am currently looking for a (media) computer, so (in no particular order):
     1. Processor speed
     2. Bus speed
     3. Memory
     4. Benchmarks in applications I will be using
     5. Video Card
     6. Audio Card
     7. Attractive case
     8. Remote

  4. My favorite processor (well, microcontroller) is the Atmel ATTINY11, which goes for 54 cents a piece on DigiKey. It may not be top of the line, but you can’t beat it for low price.

  5. Three things I want to learn in this class are:
     1. How to best make use of a processor
     2. How to design advanced board level circuitry
     3. How to actually use Verilog

• ErinKelly

  1. I’m taking this class because I know absolutely nothing about a computer, and I’d like to remedy that and learn at least something

  2. Computer Architecture is the theory and fundamental operating structure of a computing system. Most commonly, a computing system is a computer. (http://en.wikipedia.org/wiki/Computer_architecture)

  3. I have yet to buy a computer save through Olin. I think I would look at price, speed, and reliability, but I wouldn’t know how to compare them, or what the speed and reliability are worth
  4. I think that intel’s 8088 processor is kind of cool because it was behind the first IBM PC
  5. 1. How logic can turn into something so complex as a computer
     1. How to value things about a computer, e.g. for buying
     2. What machine code looks/feels like

• KellyButcher

  1. I want to understand computing from basics.
  2. How to put together systems that carry out logical calculations.
  3. What I can afford that will run the software I need, with much advice from more knowledgeable people.
  4. I suppose a dual-core Athlon, because that is what I have just been instructed to buy.
  5. Things to Learn
     1. So just how do you put together simple logic to flexibly perform so many varieties of operations?

     2. What are all the acronyms from the Welcome PowerPoint?

     3. Verilog...never heard of it before Friday, but it sounded exciting

• ScottMcClure

  1. I am taking this class because the geniuses that possess power over scheduling decided it would be a good idea to move Software Design, a standard sophomore class, into a time that conflicts with other standard sophomore classes so I went to LCanavan and got her to give me the first class that was a requirement for ECE that had spaces.
  2. Computer architecture is the organization of different portions of a machine required creating a system that efficiently receives an input, processes that input and possibly stores the results for the future, and outputs based upon its current state.
  3. Price and maintainability. Even for computing-intensive tasks, it doesn’t pay for me to be on the leading edge of technology. Also, I want a computer that is usable and fits what I need it for (laptop/desktop).
  4. PIC 8 bit microcontrollers. I have never done much low level work unless it is on embedded stuff, and I think I have an idea of how the internals of the relatively simple micros from reading too many datasheets.
  5. FPGAs would interest me. I can’t go into much more depth because my knowledge of FPGAs isn’t very good.
  6. I would like to learn more about embedded applications for processors and how processors are designed for more specific applications besides just general computing, for instance.
  7. I would like a better familiarity with the current technology being used in processors today not too in depth, but still enough to be able to get an idea what the new processor buzzwords really mean from a design perspective.
  8. I would really like to be able to convert between base 16 and base 10 in my head.

• JohnMorgan

  1. I am taking this class because Computer Architecture is pretty much the thing I'm most interested in studying. I also think it will help me to be even more sure that I want to be an ECE.
  2. Computer Architecture seems pretty straight forward. I'd say it's the design of a computing machine.
  3. Well I used to look for something that was as huge, expensive, and massively parallel as possible (which didn't work so well with a rather modest budget). Then I decided I'd rather get something small and efficient. Lately I have decided that I should really be looking for a computer with a working BIOS. I'm still bitter about this.
  4. I'm not sure what my favorite processor is but it's certainly not anything 80x86 flavored. Backward compatibility frustrates me.
  5. 1. I want to learn how to map high level logic onto low level hardware.
     2. I want to work more with reconfigurable computing.
     3. Additionally I'd like to learn more about alternative methods of computation.

• NickHays

  1. I am taking this class to better understand computers, fill a gap in my knowledge, and have fun (the nerdy ECE kind of fun).
  2. Computer architechure is the assembling of basic logical elements to create a system capable of storing and processing information.
  3. I typically build my own, looking at individual part specs.
  4. The Athlon 64, just because I remember being excited when it came out.
  5. 1. I would like to understand how basic logical elements can combine to create something that connects me to my friends, my music, the worlds events, and countless other things.
     2. I would like to learn about FPGAs and how to program them.
     3. I would like to understand the various architechures today and how they might change in the future.

• JonPollack

  1. I'm interested in how computers/processors are built (I'm also interested in graduation)
  2. "Computer architecture is the conceptual design and fundamental operational structure of a computer system." -wikipedia
  3. I look for something cheap and how well it will run recent video games.
  4. I'm not really sure if this is a valid answer but I've always been interested in the non binary processors.
  5. FPGAs, Parallel Processing, Alternatives to binary computing,