From: "David S. Miller" <dm@neteng.engr.sgi.com>
To: linux@cthulhu.engr.sgi.com
Subject: well it is about time...
Date: Sat, 8 Jun 1996 05:19:46 -0700 [thread overview]
Message-ID: <199606081219.FAA08535@neteng.engr.sgi.com> (raw)
This port is going like a funeral procession, I apologize.
Ok, quick report:
1) Interrupts work, with a little more coding it will handle the
setup and registering of all interrupts and handlers on the
INDY for whatever driver requests them.
2) Timers work, I am using the r4k counter/compare register timer
mechanism because of the bug in the i8254 Intel timer chips
on certain INDY's. The calibration of the compare offsets
needs some work but the working framework is there and needs
a little tweaking, basically my algorithm is:
a) setup i8254 counter 0 and counter 2 such that the period
of counter 0 is the desired HZ value
b) poll counter 0 waiting for a value of 1
c) quickly set CP0_COUNTER to zero
d) poll counter 0 for value of 1
e) quickly read CP0_COUNTER value
This seems to approximate the value I want in it's current form
pretty well. I have to add some fuzz factors into it and possibly
write the calibration code in assembly to get the accuracy I
want/need.
3) The kernel boots decently far. It init's all of memory management,
sets up the buffer cache, sets up the inode table, inits the
networking stack, prints the linux banner and is about to fork
off the init kernel thread.
At this point my task list looks like:
1) Clean up and finish all the krufty code I wrote tonight ;-)
2) Write console/keyboard/mouse/serial drivers as these will need to
be done anyways.
3) Do some verification on what works at that point.
4) Look into getting kgdb working.
5) Write ethernet/scsi drivers.
6) (fingers crossed) shell prompt... we hope...
As far as I'm concerned I am severely behind schedule. I will try to
get the pace going more quickly soon, I promise. Sorry. God, I'm
so slow, two weeks to get the thing to half boot, sheesh!
Later,
David S. Miller
dm@sgi.com
next reply other threads:[~1996-06-08 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-08 12:19 David S. Miller [this message]
1996-06-10 16:59 ` well it is about time William J. Earl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199606081219.FAA08535@neteng.engr.sgi.com \
--to=dm@neteng.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.