R. Clayton (rclayton@monmouth.edu)
(no date)
You mispelled yield as "yeild" in the system_call section of system.h.
Fixed; thanks.
What is the system_call 0 or "_must_be_first" supposed to do.
It serves a purpose, but none that you need to worry about. I've changed the
name to _must_be_first_and_should_be_ignored_because_it_is_not_a_system_call_
i get an interrupt 20 handler error, even though there arent 20 interrupts
defined? Is this the idle interrupt or nothing to do interrupt?
I'm not sure I understand the question, but your operating system should be
able to handle unrecognized system-call numbers. The easiest way to do that
is to ignore the system call and get rid of the process that made the call.
I'm hazy on the actual reading from the disk. When you use the
disk_io::read, does that automatically read in the whole disk to the user
space? How does the data get into the user space?
You probably want to review the second paragraph in the disk command register
description, the paragraph that starts "Writing the value device::read to the
Disk Command Register initiates..."
When does the os ask for the disk name? Where does it know to read that
from?
You probably want to review the second paragraph of the Running the Simulator
Section in the architecture simulator page, the paragraph that begins "By
default, the simulator looks in..."
This archive was generated by hypermail 2.0b3 on Fri Dec 03 2004 - 12:00:06 EST