If you all check your data directories, you will find information stored in your results.asm.assignments files.

For those who had Data Structures last semester, you'll recall the weekly commit/wiki assignments… this is the same. Basically, I'd like for everyone, each week (essentially from Sunday through Saturday) to perform:

• 2 repository commits (to the cpu simulator project repository)
• 2 wiki edits (eligible edits are done on the course notes wiki)

I have combined the first two weeks, and ran the entry for last week… so we're up-to-date as far as that is concerned. This weekend, the check for this week's efforts will be run.

Be sure to check and see if anything is inconsistent.

And if you find you missed one of the items, there are opportunities for extra credit, so you can make up any such missed opportunities by working a little harder and doing more (more is always good). And please, don't try and skimp by with “empty” commits/edits.. if I notice them I will enact the smite() member function of the lightning_bolt class (inherited from the Zeus base class).

A recurring theme I've had when speaking to different people is that the material we are learning and components implementing really are not that hard… it is just very easy to look at it the wrong way and think it is much more difficult than it is.

The best solution to feelings of confusion is to ASK questions and TALK to others. We've had many conversations in the class IRC, and the mailing list has seen some use, along with useful information being put up on the class wiki. These are all good resources, and we should all strive to make the most of them.

To further reduce confusion, especially in the “who's doing what” category, has been an effort to identify (at least each week), who is working on what… so we all can have a clearer idea on things.

If you look on the wiki, you'll see such a section up at the top… if you find information is incorrect, please update it. If what you are working on changes, please change it.

Especially as we're getting to a point where we're starting to see actual processor implementations, communication will be even more important than ever.

So far, it seems there are two strong efforts by various members of the class to implement the Intel 8085 and the MOS 6502 CPUs. In fact, an 8085 directory has already appeared in the repository with code being implemented.

I suspect the 6502 camp will be along in short order.

These are not the only choice available– if you want, other processors are still available, OR you can join any of these existing efforts.

Brian and John are spearheading the 8085 development at this point. If you'd like to help out, talk with them to get a sense for an overall gameplan.

Brad and Anthony have so far expressed an interest in the 6502 implementation.

Many of us have been digging up information on the various processors. Remember to update the wiki with any useful links (there's now a References section).

Even though this is an internet course, it really only means there's no set established classtime. If you'd even want to come in and chat up others (me included), feel free to do so… the following times I have scheduled as “lab hours”:

• Mondays 3pm-5pm (sometimes I have a Monday afternoon meeting– currently those days will be 3/14, 4/18, and 5/9)
• Fridays 3pm-5pm
• Tuesdays 5pm-6pm

Additionally, there is considerable overlap in this class and my two HPC courses… so if you're free and want to come in (even if just to work on stuff), the following times can also work:

• Mondays 12:20-2:20pm
• Fridays 12:20-2:20pm
• Tuesdays 9:35am-11:35am
• Thursday 9:35am-11:35am

While we may be working on class-related projects, there is often time to have mini conversations about Computer Organization… but as I said, even if you just want a place to come and work on things… there are more than enough free seats you can use.

At the time of this writing, the repository is at revision 108. Be sure to do an “svn update” if you haven't done so lately.

And again— you NEED NEED NEED to commit as you're working on stuff… get out of the habit of committing only finished, working code. Partial and in-progress commits are vital to avoiding confusion and keeping things flowing smoothly, as well as doing a regular “svn update”

I think probably the largest stumbling block standing in the way of true awesomeness flowing is people holding back on commits and communication. Remember, aside from a couple people, most of you have not had any experience in this area… nor are you expected to… in fact, that's what the class is for– to learn about this stuff, and apply it to what we're doing (creating the CPU simulator).

If you think you have a stupid question- GREAT! Ask it. If you're not getting something, ASK! There are also plenty of resources available on the Internet, and the LAIRbrary has seen a lot of activity checking on its various books.