From owner-freebsd-mips@FreeBSD.ORG Sat Mar 13 14:24:37 2004 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 1EAC216A4CF; Sat, 13 Mar 2004 14:24:37 -0800 (PST) Date: Sat, 13 Mar 2004 12:24:37 -1000 From: juli mallett To: freebsd-mips@FreeBSD.org Message-ID: <20040313222437.GA46319@FreeBSD.org> References: <20040313034439.GA58568@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040313034439.GA58568@FreeBSD.org> User-Agent: Mutt/1.4.1i X-Negacore: Yes X-Authentication-Warning: localhost: juli pwned teh intarweb X-Disclaimer: Opinions expressed about the deliciousness of eating brains are my own unless expressed by my employer. Subject: Re: current status update.. X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Mar 2004 22:24:37 -0000 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 [ 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@freebsd.org. adrift in the pacific. > _______________________________________________ > freebsd-mips@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mips > To unsubscribe, send any mail to "freebsd-mips-unsubscribe@freebsd.org" -- juli mallett. jmallett@freebsd.org. adrift in the pacific.