I haven't posted here on the TECS forum since the subject I was teaching (using the TECS book) finished in May, but I thought I should say thanks to all the people who helped me with my questions and gave me ideas for my teaching.
Unfortunately, after running TECS as a pilot subject it's been decided to go back to a more traditional computer architecture/operating system format for the subject, and I've been busily writing the material to run the new course sometime in 2011.
TECS has really helped in my understanding of how the CPU works internally, and I've just finished building a hardwired CPU using the Logisim simulator. Next, I'll try designing a microcoded CPU.
So thanks again for all your help here, and best wishes for the festive season!
P.S. Comments on my notes so far would be much appreciated, and if anybody can tell me how to correctly output an overflow status line in a twos-complement ALU, that would be excellent.
Can you give any information as to why your college
made this decision?
TECS is such an efficient course it's hard to see how
devoting the same amount of time could give a better
Having said that I still haven't managed to get around to
Happy Christmas to you too
On Mon, Dec 20, 2010 at 03:01:32AM +1000, culchie wrote:
> Can you give any information as to why your college
> made this decision?
> TECS is such an efficient course it's hard to see how
> devoting the same amount of time could give a better
> Having said that I still haven't managed to get around to
> finishing it!
> Happy Christmas to you too
Thanks for the mail culchie.
TECS is great, don't get me wrong, but it's more of a capstone subject that
students should do after having seen a range of other material. TECS goes for
depth and active learning but at the expense of breadth of coverage.
For the subject that I'm teaching, we need 6 weeks of operating systems,
which TECS doesn't cover in enough detail. Other things which we need to
- the CISC vs RISC distinction
- instruction set design and ISAs
- the various addressing modes
- user mode vs kernel mode
- interrupts, exceptions, syscalls, and handlers for them
- low-level memory management: pages etc.
- processes & process scheduling
- file systems
- memoy management: pages, paging, COW
- synchronisation and threads
So, having done this subject which cuts a broad swathe across both the
hardware and software sides of systems, students could then go on to do
TECS which covers some of the material but in more depth.