From owner-freebsd-mips@FreeBSD.ORG Sun Jul 2 17:05:45 2006 Return-Path: X-Original-To: freebsd-mips@freebsd.org Delivered-To: freebsd-mips@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8B9816A590; Sun, 2 Jul 2006 17:05:45 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F4B64455B; Sun, 2 Jul 2006 17:05:44 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [IPv6:::1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k62H5WId032137; Sun, 2 Jul 2006 11:05:32 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 02 Jul 2006 11:05:34 -0600 (MDT) Message-Id: <20060702.110534.43008234.imp@bsdimp.com> To: gonzo@pbxpress.com From: "M. Warner Losh" In-Reply-To: <44A54061.8090102@pbxpress.com> References: <44A54061.8090102@pbxpress.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: jmallet@freebsd.org, freebsd-embedded@freebsd.org, freebsd-mips@freebsd.org Subject: Re: MIPS32 support X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 17:05:45 -0000 In message: <44A54061.8090102@pbxpress.com> Oleksandr Tymoshenko writes: : Hello people. For last few weekends I've been tweaking code of latest : freebsd-mips snapshot, provided by Juli, intending to run it on MIPS32 : evaluation board I'd got. On the moment I have some low-level stuff : ported: TLB handling, traps handling, interrupt handling. Kernel boots : and runs on a board(well, till a certain moment of course, there is no : PCI bus support yet). Not many changes to original code, but it took a : while to look through architecture specs. Now, when I know where to go : further with porting, I'd like to put my changes together, clean them : out and keep in sync with main development branch. The latest available : sources are more then one year old. Was there any progress since then? Also : there is a question of keeping mips64/mips32 sources together. NetBSD : keeps code for both platforms as one meta-architecture "mips" and manage : it with #defines from architectures like "evbmips". It's only mips64 : tree in the snapshot so far. So I wander if there is a kind of roadmap : for freebsd-mips project. Thanks! The FreeBSD mips project has been an on again off again affair for a number of years (like 8). Juli stopped working on the mips64 port last year. She had made good progress on this port, but I don't think it ever was a complete port. Lots of stuff missing, and aimed at the 64-bit server market. Since MIPS is basically out of that market, there wasn't much interest in pursuing this. At BSDcan, a number of us got together and resolved to resurrect the FreeBSD/mips port. We started a private p4 repo directory and made a little progress before the conference was over. I'm in the process of moving the work that was done to a public portion of the p4 server. I'll post details when the operations are complete. The roadmap forward will be in this tree, and we're planning on using FreeBSD/arm as a model, for the moment. In FreeBSD/arm, we merge the src/sys/arch/arm and src/sys/arch/evbarm trees. There's not a lot of need to keep them separate. Until we have a radically different arm/mips port, I think this is the way to go. So, if you'd like to get involved and help out on this project, drop me a note and we'll see about getting p4 access for you. Warner From owner-freebsd-mips@FreeBSD.ORG Sun Jul 2 17:47:30 2006 Return-Path: X-Original-To: freebsd-mips@freebsd.org Delivered-To: freebsd-mips@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EFCB16A403 for ; Sun, 2 Jul 2006 17:47:30 +0000 (UTC) (envelope-from tiffany.snyder@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02FB843D46 for ; Sun, 2 Jul 2006 17:47:28 +0000 (GMT) (envelope-from tiffany.snyder@gmail.com) Received: by py-out-1112.google.com with SMTP id c63so854460pyc for ; Sun, 02 Jul 2006 10:47:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=FVoukqZOTQhs1A+2sK+Em52z40yBJOVkBA1v0r0YblJ1bazXlvrPcvNm9wQQyFCL++ZE0UCYfU4+Ssxxsm6QKTzxne5p+Yv6/aZ1h08TMXXv+QWmohHoLE7MOF90KEqn7QB1hVvhtkh37Aru3CVWYBd52vxs+qLiZRmbpGYmcVE= Received: by 10.35.60.16 with SMTP id n16mr300855pyk; Sun, 02 Jul 2006 10:47:28 -0700 (PDT) Received: by 10.35.119.18 with HTTP; Sun, 2 Jul 2006 10:47:28 -0700 (PDT) Message-ID: Date: Sun, 2 Jul 2006 10:47:28 -0700 From: "Tiffany Snyder" To: "M. Warner Losh" In-Reply-To: <20060702.110534.43008234.imp@bsdimp.com> MIME-Version: 1.0 References: <44A54061.8090102@pbxpress.com> <20060702.110534.43008234.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: jmallet@freebsd.org, gonzo@pbxpress.com, freebsd-embedded@freebsd.org, freebsd-mips@freebsd.org Subject: Re: MIPS32 support X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 17:47:30 -0000 I agree MIPS fell out of the server market but the embedded market more than offset that. The company I work for has been a FreeBSD user for a number of years. So, we use FreeBSD on our Intel based gears and NetBSD on our MIPS based gears. We'd like to standardise on FreeBSD including MIPS. This thread is the only encouraging email I've seen in the past 5 years on MIPS. I hope it lasts!. Thanks, Tiffany. On 7/2/06, M. Warner Losh wrote: > > In message: <44A54061.8090102@pbxpress.com> > Oleksandr Tymoshenko writes: > : Hello people. For last few weekends I've been tweaking code of > latest > : freebsd-mips snapshot, provided by Juli, intending to run it on MIPS32 > : evaluation board I'd got. On the moment I have some low-level stuff > : ported: TLB handling, traps handling, interrupt handling. Kernel boots > : and runs on a board(well, till a certain moment of course, there is no > : PCI bus support yet). Not many changes to original code, but it took a > : while to look through architecture specs. Now, when I know where to go > : further with porting, I'd like to put my changes together, clean them > : out and keep in sync with main development branch. The latest available > : sources are more then one year old. Was there any progress since then? > Also > : there is a question of keeping mips64/mips32 sources together. NetBSD > : keeps code for both platforms as one meta-architecture "mips" and manage > : it with #defines from architectures like "evbmips". It's only mips64 > : tree in the snapshot so far. So I wander if there is a kind of roadmap > : for freebsd-mips project. Thanks! > > The FreeBSD mips project has been an on again off again affair for a > number of years (like 8). > > Juli stopped working on the mips64 port last year. She had made good > progress on this port, but I don't think it ever was a complete port. > Lots of stuff missing, and aimed at the 64-bit server market. Since > MIPS is basically out of that market, there wasn't much interest in > pursuing this. > > At BSDcan, a number of us got together and resolved to resurrect the > FreeBSD/mips port. We started a private p4 repo directory and made a > little progress before the conference was over. > > I'm in the process of moving the work that was done to a public > portion of the p4 server. I'll post details when the operations are > complete. > > The roadmap forward will be in this tree, and we're planning on using > FreeBSD/arm as a model, for the moment. In FreeBSD/arm, we merge the > src/sys/arch/arm and src/sys/arch/evbarm trees. There's not a lot of > need to keep them separate. Until we have a radically different > arm/mips port, I think this is the way to go. > > So, if you'd like to get involved and help out on this project, drop > me a note and we'll see about getting p4 access for you. > > Warner > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org > " >