From owner-freebsd-mips@FreeBSD.ORG Tue Apr 29 00:19:52 2003 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 01F7C37B401; Tue, 29 Apr 2003 00:19:51 -0700 (PDT) Date: Tue, 29 Apr 2003 02:19:51 -0500 From: Juli Mallett To: freebsd-mips@FreeBSD.org Message-ID: <20030429021951.A31541@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Title: Code Maven X-Towel: Yes X-Negacore: Yes X-Authentication-Warning: localhost: juli pwned teh intarweb Subject: Current status of FBSD/MIPS(sgimips) 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: Tue, 29 Apr 2003 07:19:52 -0000 Hey, So after a weekend+ of integrating code from NetBSD and testing and so on fairly steadily, the current status is: the kernel boots up to the copyright... it tries to go a little further but inadequacies of VM and pmap mean that it blows up a little bit after that. the watchdog initialises.. we switch from the boot exception vector to our own. unless there are printfs or other such fluff in various places, the kernel blows up in deterministic but non-sensical ways. cpu information is printed prematurely to make sure things are going fine. Important code like cache control stuff and exceptions and the 'ip22.c' file and related infrastructure from NetBSD have been brought over, and it's getting fairly trivial to bring over more mips code from NetBSD. That is less true in the case of pmap or device drivers, of course. Anyone with p4 access who wants to double-check, fix, test, or clean up what's there is welcome to. I will try to get a new diff generated some time soon, but I'm still lagging behind with getting a few local hacks either into p4, or reverted. Thanx, juli. PS: I've been doing all my testing on a purple R4400 IP22 (250MHz), teal R4400 IP22 (175MHz), and a R4600 Indy (133MHz), with the latter beign the least tested, as the nature of the beast is quite icky. -- juli mallett. email: jmallett@freebsd.org; aim: bsdflata; efnet: juli;