This homework is due at the beginning of class Tuesday, 9/4/2007.

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

Questions

Register on this Wiki and add yourself to Fall 2007/StudentList
Buy the textbook (see Fall 2007/Course Syllabus)
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.

Kevin Sihlanick

I want to learn how computers work at a lower level so that I can do more embedded design work. And it's required.
Computer Architecutre is the study of how and why computers are built and used as tools to solve problems.
I look for a computer with a standalone graphics processor and graphics memory. Otherwise, I haven't kept up with it enough to understand processor differences anymore, they have so many names and its a pain to find real data on specific processors. Memory is always good too.
I like the PIC18F. I know how to use it, it's cheap enough to get parts and a PICKIT2, and is versatile enough to do most of what I need to.
I want to learn: Digital logic, how to use verilog and the applications it is good for, and hopefully how to develop for FPGA's.

Molly Crowther

I am taking this class because I wanted a hardware class to round out my electrical engineering core for E:SYS. And I heard it was a cool class. And maybe my dad won't make as much fun of me for not knowing much about computer hardware.
I think of computer architecture as the stuff we always sort of gloss over at the beginning of software classes, like stuff with binary and assembly and little bits of metal and wires.
The last time I was involved in the purchasing decision for a computer was when I was around 13. I was being forced to get a mac, and I chose one of the original clamshell iBooks because it looked nice, even though it didn't have a floppy drive *sigh*.
I like processors that work and do things for me. I'm sure when we get around to making them, the one we make will be my favorite. I guess PICs are okay.
I want to learn more about logic circuits, more complicated math circuits (sort of how this all fits in with some of the circuits we made in modcon, if it even does), and the whole systemsy view of a computer.

Bennett Chabot

I'm taking this class to build a base of knowledge about how computing works, its powers, and its limitations.
CompArch is a course @ Olin taught by the illustrious Mark Chang. Its content comprises the concepts of computer logic and processor structure that can perform computations and run programs.
Hard drive size, graphics card, A/V abilities. Processor speed and RAM would be optimized within a price range.
As a specific character, I have to give props to the Intel centrino in this good ol' Dell D610, because this *particular* processor has processed a lot of good stuff for me in the last couple years, and its the first that has exclusively belonged to me.
I want to learn: a) how computers handle information on the lower levels and what that means for how to talk to them b) what is changing in the field of computing that will change the way people interact w/information c)how could I best assemble components for a devastating pc to run Fallout 3 next fall.

Chris Nissman

I've developed an overwhelming urge to actually understand some of the fields in specs sheets mean, beyond lower is better, higher is better, etc.
CompArch is the source of all of those tri-Color diagrams which accompany every CPU and GPU release for mainstream computing, which I have only the slightest idea what it means. That and, you know, computer logic and the interaction between... components... and ...stuff?
How long I think the mobo chipset is going to have new processors coming out for it (futureproofing... sorta). I've never bought a prebuilt computer aside from the required Dell laptop, and next time I'm whiteboxing my laptop too - so each part is evaluated individually using spec sheets and what reviewers say online. I don't particularly want to spend the whole page on this. You can talk to me later if you want to know more about the obscene amount of time I spend looking at computer "stuff".
I'm fond of the Core 2 Duo's right now, because lets face it - its whats hot in the enthusiast segment. Who doesn't love procs that are hitting +44% FSB with stock cooling; also I'm just glad to see something coming out of Intel that isn't Netburst. On the other hand I'm terrified that AMD's upcoming 65nm's won't be enough to help them regain their tiny fraction of the market share, esp. with 45mm Penryn approaching.
I want to learn: a.) What makes Core 2 tick? b.) Why laptop manufacturers can't manage to actually adhere to the MXM standards with more regularity. c.) What actually goes on in the north bridge chipsets... and now I want to go talk to Bennet about Fallout 3.

Matt Aasted

I am taking this course so I can learn to write better Verilog to perform computation and so that I can build a processor in Verilog which actually executes instructions.
Computer Architecture is the parts of computer hardware design from the gate level up. It's not concerned with what's actually performing the logic, but is instead concerned with designing logical topologies to make computation happen.
When buying a computer, I mostly optimize for cost -- using parts that are 6 months old and have good reviews is the name of the game. I also try to optimize for low power, low noise (mechanical, typically) and performance which I generally look at in terms of number of cores, amount of ram, type of graphics card etc.
C does a pretty good job of abstracting away particular processors, but if I had to write assembly I would want to write for a RISC processor like an ARM. I appreciate the x86 for being my main computation hog, but I wouldn't want to write assembly for it.
I want to explore parallel processing metaphors because I think they're where the future is, I'd like to learn a systems view of a computer (what is a northbridge and why do I want one?), and I'd like to learn more efficient logical structures for FPGA development.

Joe Funke

I hope to use this class (which to me sounds like the most interesting ECE course) in comparison with an ME class to get a sense of the differences between ECE and ME as possible majors.
I see computer architecture as the method by which massive amounts of data (ones and zeros) are organized into complex hierarchical systems that can become a usable and pliable device.
When looking at a computer, the first thing I consider is the motherboard and how upgradable it will be down the road. After that, its processor speed and type (front bus speed), memory bandwidth, and graphics card.
Hmm...so I’m not even sure if we are talking PIC-like processors or computer processors. I don’t know enough about microprocessors to have a favorite (I guess PICs?), but as computers go, I hear the intel 2 duos are quite nice. I would also be curious as to what the differences are between computer processors and microprocessors.
I hope to better understand how a computer can turn ones and zeros into a usable device, how circuits make decisions, basic low level coding, and see what goes into ECE in general.

David Nelson

I am taking this course to learn how computers work, since a transistor is the most complicated device I sort of understand at this point.
Computer architecture is about using hardware, firmware, and software to turn a bunch of electronics parts into something that can play Fallout 3.
I’d look for something that’s affordable, but will still run programs that will be coming out for at least the next year or two.
I’m a fan of the AMD Athlon processor that was in my first computer, even though I don’t even remember any of the specs.
I want to learn about (a) processors for mobile devices, (b) assembly code, and (c) parallel computing.

Boris Dieseldorff

I'd like to learn what makes a computer tick. Curiosity tends to be in the driver's seat where I'm concerned.
I see computer architecture as the engineering that makes a computer work efficiently and effectively.
I don't game on my computer or do intensive video or audio processing so most modern computers suit me just fine. I look for something that will allow me to run a large number of programs without considerable slowdown and will be able to store everything I need access to easily. I pretty much see computers kind of like cars in that you buy one, use it for a few years and then buy another. Except you can use old computers as servers and old cars only work as hickish lawn ornaments.
I don't really know much here, but AMD has always seemed nice. Processors in computers don't seem very personal to me though. I tend to fall for things like PICs. Oh and Spartan3 FPGAs are sexy.
I'll go with doing cool things with FPGAs, writing verilog decently (this is kind of double-counting but whatever) and gaining an understanding of computer logic.

Aisaku Pradhan

I once had an internship where i gathered data and took them to "computer architects" who looked over my data nodded a little bit ordered some changes to a computer chip and handed me a new chip a week later. They never really gave me a straight answer on what exactly those numbers meant. Even though I dont remember the numbers, I am still bitter and want to know. And its required.
Computer Architecture is the design of a computer. While a traditional architect designs blueprints for buidings and creates functional uses from space, a computer architect bluprints computers and creates functional uses from things like silicon.
Novelty is pretty cool, but thats expensive. Right now I like low power and good number crunching ability. Efficiency seems to be king. I also like the names Conroe, Merom and Nehalem because i did grunt work validation on them.
I have a particular affinity for the Intel Prescott family of chips because its the only consumer chip that you could use as a stove in a pinch. Also the Core 2 Duo T2600's are nice in terms of processing power per watt.
I want to learn about GPU's and what makes them so different than standard CPU's. I also would like to learn about parallel computing and distributed memory.

Kiralyse Gonzalez

I'd like to know how a computer works because I don't really have any idea. Also, the class was recommended to me by my advisor.
Its the study of designing computers?
I don't really know much about computers, but in general I'd look for a small form factor, and a reasonable price.
I don't have a favorite processor because I know nothing; however I will say a food processor just to amuse.
I'd like to learn more about processors (so I could possibly answer question 4), enough information to be a more discerning computer person, and... well... parallel computing sounds cool?

MattCrawford

First, it seems pretty cool to know how a processor works. Second, it continues my theme of "well that part of the computer was pretty cool, but how do all the functions it depends on work?" (application programming in software design, lower-level programming and kernel design in software systems, and now processor internals). Third, it is required.
Computer architecture is the study of the digital logic circuitry used in the hardware of computers. It also involves the design and improvement of processor features useful in the implementation of operating systems and other software.
Price is important but it must have plenty of RAM (no less than 2 GB ever, and at least 4 GB in a "serious" desktop). CPU speed is not that important, but a multi-core processor is a plus. Hard disk size is no longer a serious concern for me because I use external drives for most of my storage. Finally, I really don't care about the graphics because I doubt that Firefox or Outlook will require 3D anytime soon.
- Later addition: Having lots of ports, in terms of both many different types of ports and several ports of the most common (read USB and Firewire, multiple NICs would also be nice), is a good thing. But it has to still have a serial port.
My favorite processor is the Motorola 68000 (and derivatives), primarily for historical reasons. I also admire the Zilog Z80 for its longevity and continued relevance in low-cost, low-performance systems. Finally while I like the way Intel (and recently AMD) has modified the x86 family to provide ever-greater performance, I want to mention that it's a complete hack.
I want to learn about the middle ground between logic gates and processors (that is, I understand gates and I understand the entire processor, but how do you make a functional processor from those gates?). I also want to learn about some of the choices made in the course of designing a processor. Finally I would like to learn about some of the ways to improve processor performance other than increasing clockspeed.
- Later addition: Learning to do cool things in Verilog would be nice too (it got my cousin a job at this sweet UAV company, so it can't be too bad)

RyanHubbard

Nearly everything I deal with as a systems engineer will have an embedded computer or processor of some kind (well, except for that whole woodburning stove thing that's my scope project), and it would be useful to understand how they fundamentally work and how that effects their interactions with the rest of the system. Plus, it sounded like a fun class.
The study of the individual components that together produce the emergent behavior of turning ones and zeroes (or for that matter, electrons) into half-life2.
I look for a system that can fulfill my basic requirements, is inexpensive, and plays nice with ubuntu.
No idea... but I liked those commercials that the blue man group did with intel.
A. I would like to gain some knowledge of the computing theory in general. B. I'm specifically very interested in the design of complex embedded control systems such as those used in rocket guidance. C. As a random bit of knowledge, it might be sweet to know how to build a cheap beowulf cluster: http://www.calvin.edu/~adams/research/microwulf/

ConnorRiley

I wanted to take a Mark Chang class before I graduate. Also, I think it's very uncool to pretend that your computer just sort of works by magic, or that low-level processes don't affect you. So this is me being one less person buying into the no-user-servicable-parts-inside trend.
Computer architecture deals with all of the layers of abstraction between the transistors and the OS. This class will probably focus on de-mystifying the lower levels, like chip layout, logic and assembly.
I can't afford cutting-edge, and I'm not interested in spending a lot of time overclocking or watercooling a system, so mostly just spending as little as possible while being able to play cutting edge games for the next few years.
All the cool kids like Intel these days, which means I'm sticking with AMD while they're cheap. I only want to play Portal, anyway.
Chip design, assembly language, how to make an FPGA dance.

DanCody

To get a better understanding of assorted computing topics, learn about hardware description languages, and play with FPGAs. Also, it'd just be cool to build a processor.
How to hook some basic building blocks together to make something that can solve algorithmic problems.
Price, memory, processor speed.
Ummmm . . . something embedded. 'Cuz interacting with the real world is cool.
(a) Reliability. How do you design a control system (or whatever) such that you're comfortable with someone entrusting their life to it? (b) FPGA thingies. I don't really know what they're about but I feel like I should. (c) An understanding of the design differences between common processor types.

MichaelBoutelle

I am taking this class because I would like more than the abstract concept of the computer processor that I currently possess. That is to say, given the ubiquitous presence of processors in my life, I feel obligated to gain an understanding of these devices that does not rely on magic to fill the vast holes in my comprehension.
Computer Architecture is the layout of electrical hardware components that go into a computer.
When buying a computer, I research which parts offer the greatest performance/price ratio for my needs and assemble the machine myself.
My favorite processor is the Athlon 64 “Clawhammer” because it was very fast at the time, it was very efficient, it evokes nostalgia in me, and it has an awesome name.
I want to learn how exactly software and hardware interact, how the individual components of the computer interact, and what branch prediction is and why it matters.

LyndseyStadtmueller

I'm taking this class because I realy have no idea how computers work, and I wanted to complement my software design class for systems by learning about some hardware.
Computer architecture is the physical building of a computer -putting together a bunch of electrical hardware to make electricity turn into games and homework assignments and such.
I look for a something with a good price and memory enough to easily handle whatever I plan on using the computer for.
see #1. I have no idea how computers work, and only a slightly better idea of the components.
It would be nice to learn something about processors, if only to be able to answer the previous question. Right now I'd have to say I want to know more about the basic ideas behind computing, how electricity turns into all the awesome things computers can do, and about all of the communications that computers are capable of (both within the computer itself and to outside devices).

Ginneh Cornelius

I needed another ECE core and this class seemed interesting and I could use the knowledge. An added bonus is that when guys find out I am an engineer their first response has a 78% chance of asking me about my favorite processor or os. I would like to not have to nod my head and make noncommittal statements using the small amount of information I have gleaned from my friends and actually be able to respond.
Off the top of my head, I would say it is the structure of coding in hardware components used to build a computer. Stuff like gates and switches. This courses outline leads me to believe that it is also the integration of these hardware components with each other. http://ca.olin.edu/cawiki/Fall_2007/Course_Syllabus. I did go to wikipedia and it seems that I am sort of right.
I've never really bought a whole computer myself (except for the mandatory lab top). We've always had a pc and my dad would take me to computer fairs to get new parts for it. We would first look for anything that could do what we wanted. Then out of those, we would go on the most bang for our buck philosophy. My dad kept on and on about what was good and what was bad but I'll be darned if I can remember anything specific.
See question number 1. I really like the kind that works for the job I want to do without too much heat.
I would like to learn how bits turn into pretty pictures, traditional and modern ways to improve the power and efficiency of processors and the overall electronic device, and about alternatives to traditional computer architecture. Also if I can learn how to answer question #4 in the process, that would be great.

AnnieMartin

Because I use computers all the time, so I should probably have some idea of how they work.
Computer Architechture is the things that make computers compute- from the circuits up to the hardward components.
I've never bought a computer, and I don't know too much about them. I think my checklist would probably be 1)Does it support the newest games coming out without being upgraded? 2)Can I afford it? 3) Which one sounds the most impressive?
???
I don't know a lot about computers or what might possibly be in them, so I feel like any real specifics I put here I'd be stealing from somebody else. I'm game for learning anything, and maybe after a couple of weeks I'll have a better idea of what it is I don't know.

PeterMassari

I am a systems engineering major, and I know very little about computers. I feel like I should take courses in areas in which I feel I am particularly weak, and thus I have signed up for Computer Architecture.
I really do not know what Comp Arc is. I have a vague idea that it involves learning about how computers work.
I have never really purchased a computer before (aside from my Olin laptop, which I did not choose), but I suspect that when I do purchase one, the thing that would matter most to me is price. The second most important thing would be the warranty because one thing 3 years at Olin has taught me is to be grateful for the warranty we have on our laptops (very few of my laptop's current components were part of it on the day I took it out of the box).
I'm not even totally sure what a processor is, much less what my favorite would be. The only one I have heard of is Intel, thanks to numerous commercials I have seen for that brand.
Can't really think of anything specific because I don't know enough about what we'll be learning in the class to frame any specific questions. If you ask me again in a few weeks, I'll probably have a better idea.

Thomas Michon

I have found that the more I know something works, the easier it is to work with and the more cool things I can do with it. After taking Software Systems, I knew how to do more things with comptuers than ever before. It opened up many new possibilities when working with files or the operating system. I expect that Computer Architecture will provide a similar opportunity.
Computer Architecture is the creation of devices that process logic. It is the amalgamation of tiny components that perform only redimentary tasks into a larger system that can perform anything a programmer can throw at it.
Usually, I look for a set of components that offer exemplary qualities for a reasonable cost. I look for the not-quite-top-of-the-line processor, a compatible and well-supported motherboard that offers only the built-in features (like network) that I need, as much high-speed RAM as I can afford, a power supply that is up to the task (and occasionally comes with my case), and then I decide what else I can afford to splurge on, or whether I'll be reusing the remaining components from my old machine.
At present, I've only worked with computers with Intel x86 processors, and truthfully I've never done much that actually concerned actual processor architecture. That said, trying to find Linux stuff that runs on an ARM processor is kind of annoying, so I would have to say that I'm really liking x86 right now.
I would love to learn about parallel computing, gain an understanding of how various devices communicate with each other (graphics, networking, etc.), and get familiar with assembler.

Kiuk Gwak

I want to learn about the fundamental processes done in computer and the composition of computer.
Computer Architecture is a studying the details of how the computer works and how it is composed, I think.
I look for most of things given from a company to customer such as RAM, ROM, CPU speed, graphic card, and etc... Also, because it is closely related to A/S, I think a brand seriously.
I don’t know much about the types of processors. I have used only Intel CPU so I’ll choose Intel again because it has worked good until now.
A.How the user interface is made. B.How the compilers are made and worked. C.How the messengers (likes MSN) are worked.

Ash Walker

I am taking this class since I like to see how things fit together in the systems perspective, and would like to see how the whole computer system works. I also like the hardware side of electrical engineering and am interested in that.
Computer Architecture is how the computer as a system works together to get 1’s and 0’s to a usable format.
I’ve not actually picked out a computer in years. However, I’d look for something that could be easily upgraded, had a good warranty, and was up to nominal performance standards.
I’ve been a fan of AMD’s lately, mostly since they seem to perform better than Intel for the dollar.
I want to learn about DSP’s, how the whole computer system works together to get 1’s and 0’s to something usable, and what are these FPGA’s and why do people love them so?.

BradWestgate

As an E:C major I should have a good understanding of the lower-level operations of a computer, and sadly I don't right now. Also I'd like to do some assembly programming, because I know next to nothing about that as well.
I think of computer architecture as the study of creating simple logic gates and combining them into a processor that can perform complicated operations.
I've never bought a computer for myself, but I would look for a good graphics card with ram so I could play the newer games. Price would be the most important consideration, though.
Pentium-M, because that's the one I've been using for 3+ years.
2 mentioned above: I want to learn assembly programming and how to combine logic gates into something meaningful. I also want to learn more about parallel processing.

AndyKalcic

I'm taking this class because I want to know how my computer works at the hardware level--I've already covered the other areas in other classes.
Computer Architecture is how a computer works at the hardware level, somehow involving the shuffling about of bits from register to register.
When buying a computer, I'd just want something that works, will continue to work for the forseeable future, and doesn't cost me obscene amounts of money. And unlike Matt Crawford, I've never had a use for 1GB of RAM on my personal computer, much less 2...
I'll go with Intel on this one--the little sticker on my laptop informs me that's what I'm using right now.
Assembly would be a good thing to learn, as well as DNA computing. I need three though, so I'll also include learning about on-chip parallelism (is that a word?).

KentMunson

I don't know much at all about computers, especially when it comes to hardware.
Sounds to me like the process of designing how to build a computer, with different goals in mind, such as size and functionality.
Haven't really done that, honestly, but if I were to shop for a computer, reliability would be my #1 priority.
I've pretty much always used Intel processors.
I would like to walk away from this class with a good 'big-picture' idea of how a computer works, also: I learned when I took Crypto here at Olin that some cryptosystems could be used with special hardware to work really fast, and others couldn't, and so it would be great if by the end of this class, if I were to read a paper on why that was, I could totally understand it.

HerbertChang

mm... computers are kinda cool. Having the opportunity to learn more about why the way computers are, and how computers could be improved, is cool too.
I don't know much beyond my impression of the terminology.. which is that of understanding why computers are the way they are, and as a result, understand what improvements can be made to make computers 'better'.
mm... CPU, RAM, and sometimes graphics card (if laptop computer, definitely battery life as well). Will take a look at the random computer accessories that come along too, but main decision occurs at, i guess, how well the computer would perform.\
mmm I actually don't know much about the processors. =-\
mmm.. seeing as I've been interested in the digital communications side of EE for a little bit, I would like to learn more about some DSPs, perhaps even some stuff about computer security, and error control that occurs within different units of the computer.

HyeonaLee

I took a similar course to this, named 'Digital Logic Design' at my University, but at that class, I designed a 16-bit-single-cycle computer with verilog language, without learning about the general computer and without actual fabrication of computer's components, so I want to learn more practical things at Olin.
It is the course for learning about the structure of computer and how to design it.
Actually, I didn't buy a computer by myself, and I don't know about computer well, but I would rather look for brand name and price. Due to the good after service from samsung, especially I like to buy one at Samsung.
I have no idea about computer components and no favorite processor, but I have used Intel pentium processor and it worked well, so I will choose it.
(1) Assembly language - It will be interesting because it is close to machine language.
- (2) About the other computer components - Due to the lack of my knowledge about computer.
  (3) Standards for buying a computer

HelenLewisRzeszutek

I am taking this course because I have to in order to graduate, but I am excited about taking it because I know very little about computer hardware and would like to learn more.
Computer architecture is the design and building of computers.
I've never shopped around for a computer, but when I do I will figure out what I need, and not get anything more. It seems like a lot of people buy the newest, coolest computer out there and then only end up using Word and the Internet, which I would like to avoid.
I don't know enough about processors to have a favorite. But if I have to say something, one that always works?
- How the basics of knowing binary and logic turn into telling the computer what to do
- - What the major components of a computer are, how they are all connected, and attributes - How to even start building my own computer (where to buy parts, where to start, etc.)

YongminJeong

1. Because the professor is really handsome. The additional reason is I have little bit idea how the computer works. It might be really important course for engineer, as seeing that all students must take this course in my home school, ICU.

2. Computer architecture is the conceptual design and fundamental operational structure of a computer system. (from wikipedia)

3. Better RAM, Bigger HDD, Faster CPU with reasonable price.

4. There’s nothing but to choose one processor, because the only processor I have used is intel Pentium processor.

5. -Have perfect idea how computer operates -How can I upgrade the computer -More advanced idea about Digital Logic than I have taken

Angela Sharer

I am taking this class because I think computers are pretty sweet, and I use them a lot, but I don't know too much about their inner workings.
Computer Architecture is about computer logic and processors (design, optimization, stuff?)... And more, probably. I don't really know, which is partly why I'm taking the class.
When I'm buying a computer, I want it to be powerful, new, and shiny.
My favorite processor: currently tied between food processors and the Core 2 Duo series. I guess that's wishy-washy, but whatever. My reasoning is thus: food processors make it easier for me to make tasty spring rolls (my favorite snack), and dual-core processors allow me to do twice as much stuff at once (on a computer), which is nice since I'm a little ADD. Hey, do you wanna go ride bikes?
Things I want to learn in this class: how computers work at a lower level (especially with regards to networks), more about parallel computing (I worked a little with pMatlab over the summer, and that was sweet, but the programming I was actually doing was a bit abstract, and I'd like to understand what was actually going on with the parallel stuff a little better), and learn enough ECE-speak to be able to understand what ECE-people are talking about. Also (and this is kind of a bonus): what's Fallout 3, and why is it such a big deal?

Bill Dvorak

I want to fill in the black box that currently exists in my understanding of computers from transistor to assembly code.
Computer Architecture is the comprehension of and design of processors, hard drives, and various i/o to build a useful machine.
Processing power, memory, mobility.
Intel Centrino, the fastest processor I have experience with.
The reason for different processors suit various applications, how to write assembly code for processors, how logic turns into simple cs commands--for, if, then, void, int, etc.

Nikolaus Wittenstein

Computers are super-cool. I know a lot about how software works but not a lot about how hardware works. I'm intensely interested in learning all about how things like logic gates and such combine to make things as complex as computers.
Computer Architecture is the field of study related to computer hardware and how it is designed, fabricated, and assembled. (source: I just made it up)
If I'm buying a desktop, then I'll make my own. I spend way too long browsing things like Tom's Hardware Guide and Newegg, then buy parts and assemble them. Actually, from now on I plan to buy solely Macintoshes, because I don't need a PC to play games anymore, what with Boot Camp and Parallels and such. I tend to look at things like processor speed, hard disk size, amount of RAM, operating system, etc.
I was going to say that my favorite processor was the PIC 18F2455, which is the PIC that we used in PoE. Then I remembered that I was trying to use three different timers on it and only the first two would work, so I don't think it's actually my favorite. Perhaps my favorite was the processor in my TI-89 original edition, a 10MHz 68k Motorola processor. I pretty much learned to program in TI Basic.
A. How threading works/how the processor switches tasks. B. I'd like to learn Verilog. I'm intrigued. C. I'd also like to learn about buses. How do chips talk to each other without screwing up or desyncing or something?

LeifJentoft

It sounds interesting to understand better what actually goes on in the chips that seem to govern our lives these days, and such an understanding would also be useful for robotics if a project requires on-board electronics. Furthermore, it will hopefully give me a jumping-off place from which to explore FPGAs and some of the other cool hardware that has applications to the robotics field.
The study of how to make hardware and software work together usefully to run programs. (sources: www.pcmag.com/encyclopedia, www.wikipedia.org)
Something that is reasonably powerful but not inordinately expensive, and recommended by the local mavens.
An Analog Devices Blackfin DSP because they are so versatile and compact for what you can do with them--from video compression to effects pedals for instruments.
I want to learn how to think about processors--about what challenges are most difficult in designing them, about what makes a good one--about how and why FPGAs are so powerful, and why a series of silicon junctions becomes something that can run a 'for' loop.

Kevin Bretney

I want to learn about how processors work and understand how to build them so that I can apply the knowledge in circuit design.
I could go find wikipedia and quote it, but before I go look it up I will give my answer: Computer Archetecture is the disign and building of computers which can be defined as a data processing system based on logic gates.
I look for a combination of the price/performance ratio and the choice of platform. I generally look for the current best mobile platform (currently the Santa Rosa chipset and Core 2 Duo) and enough RAM and hard drive space.
I am split on the matter, I am a fan of the Core 2 Duo because of the performance and scalability per watt but I also like the AMD dual core architecture and the hypertransport for multi-processor systems.
I want to learn more about how pipelines and the stages in them work. I want to learn about fpgas and how to program them, and I want to learn how basic instructions are implemented and how they work.

Andrew Price

I've heard several great reviews of the course from fellow ECEs and want to take the opportunity to develop a deeper understanding of the hardware, software, and general logic, the do's and dont's, involved in processor design.
Venturing a guess, Computer Architecture involves the design and manufacturing of processors and developing means for several different pieces of hardware to interact.
Speed and power all the way -- forget redundancy and security! FSB Bandwidth, RAM Timings, GPU Pipelines, Raid0, etc. etc.
Now I get to sound like a hypocrite -- I'd have to vote on the AMD Dual-Core Windsor or Brisbane processors, having had personal issue with the Core 2 Duo e6600. e6X00 might be the more brawny chip, but AMD has always been more than reliable for me.
I'm interested in learning more about both coding in assembly and designing in Verilog. Any infos about memory mapping and efficient writing and reading would be great. And lastly, but certainly not least, the ubiquitous anything-and-everything-about-FPGAs reply.