current status update..

[juli mallett]

So, um, now things run to SI_SUB_RUN_SCHEDULER (which is ~0, order ~0),
without interrupts.  With interrupts, I have to do a bunch of stuff to
make this work...  I've got some clock interrupts firing, and have the
Compare hackery going.  But that's making other things crash.  I think
I have to fix my context switch code, but I'm not 100% sure of that.
All I know is I get strange crashes, VERY strange ones if I don't at
least guard against interrupt nesting.

I figured people might want to know.

* juli mallett <jmallett at FreeBSD.org> [ Date: 2004-03-12 ]
	[ w.r.t. current status update.. ]
> Last night I started hacking away, and today in between work, I got
> things up to around SI_SUB_PROTO_IF, and have imc0 attaching, and
> have fixed a lot of bugs.  Now I have to start porting devices and
> busses from NetBSD, as well as fix what must be a few more bugs, since
> things are still blowing up a little.  I did context switching and
> related code so far to make a vm_machdep.c full of panic() calls not
> panic.  Uh.  Still working on SGI stuff, but looking a lot at using
> the Broadcom board cgd sent.  I'll let people know once the sbmips
> stuff does anything.
> 
> Any questions welcome, as usual.
> 
> I've started syncing the tree to an externally accessible server,
> I'll see if I can get SUP or something running.
> 
> Thanx,
> juli.
> -- 
> juli mallett.  jmallett at freebsd.org.  adrift in the pacific.
> _______________________________________________
> freebsd-mips at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mips
> To unsubscribe, send any mail to "freebsd-mips-unsubscribe at freebsd.org"

-- 
juli mallett.  jmallett at freebsd.org.  adrift in the pacific.