From owner-freebsd-mips@FreeBSD.ORG Mon Jun 29 00:51:51 2009 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 281AC10656C1 for ; Mon, 29 Jun 2009 00:51:51 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from core.tav.kiev.ua (tavex.colocall.com [62.149.10.42]) by mx1.freebsd.org (Postfix) with ESMTP id AFCE78FC21 for ; Mon, 29 Jun 2009 00:51:50 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from s0106001c10164644.vc.shawcable.net ([24.87.58.40] helo=[192.168.1.47]) by core.tav.kiev.ua with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1ML4of-0006Hy-Jb; Mon, 29 Jun 2009 03:33:50 +0300 Message-ID: <4A480BD2.8010700@bluezbox.com> Date: Sun, 28 Jun 2009 17:33:22 -0700 From: Oleksandr Tymoshenko User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Neelkanth Natu References: <58821.29900.qm@web34405.mail.mud.yahoo.com> In-Reply-To: <58821.29900.qm@web34405.mail.mud.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Core-Spam-Level: -- X-Core-Spam-Report: Spam detection software, running on the system "core.tav.kiev.ua", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Neelkanth Natu wrote: > Hi Oleksandr, > > I'll try out your patch and let you know how it goes. > > Do you have anything in particular that you will be working on in the > platform-independent part? I could help if needed. > I just tried to build several ports and see if it's going to succeed. As a result bug in pmap_qenter was fixed and threads work in FreeBSD/mips now. So far I managed to build python and perl(with system malloc) and they seem to work. More thorough testing required though. [...] Content analysis details: (-2.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60% [score: 0.5000] -0.3 AWL AWL: From: address is in the auto white-list Cc: freebsd-mips@freebsd.org Subject: Re: FreeBSD/mips booting on Sibyte 1250 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: Mon, 29 Jun 2009 00:51:51 -0000 Neelkanth Natu wrote: > Hi Oleksandr, > > I'll try out your patch and let you know how it goes. > > Do you have anything in particular that you will be working on in the > platform-independent part? I could help if needed. > I just tried to build several ports and see if it's going to succeed. As a result bug in pmap_qenter was fixed and threads work in FreeBSD/mips now. So far I managed to build python and perl(with system malloc) and they seem to work. More thorough testing required though. > best > Neel > > --- On Fri, 6/26/09, Oleksandr Tymoshenko wrote: > > >> From: Oleksandr Tymoshenko >> Subject: Re: FreeBSD/mips booting on Sibyte 1250 >> To: "Neelkanth Natu" >> Cc: freebsd-mips@freebsd.org, "Alexandr Rybalko" >> Date: Friday, June 26, 2009, 2:14 PM >> Neelkanth Natu wrote: >> >>> Hi Warner, >>> >>> I have attached the diffs against -current at revision >>> >> 194280. >> >>> There are some changes in the diff that are unrelated >>> >> to the sibyte >> >>> work and probably should be committed separately. >>> >>> I can provide more information about changes to >>> >> specific files if necessary. >> Thanks for contribution. I'm trying to make >> platform-independent >> part of mips/ tree and userland stable and once it's done >> more time >> will be available for adding new platforms (I hope it will >> be soon >> enough) :) >> Meanwhile I'd appreciate if you test attached >> patch for busdma >> with your hardware. This implementation has been >> shamelessly ripped >> from arm code tree and should handle alignment/boundaries >> limitations >> properly. If possible, test with several DMA-enabled >> devices working >> simultaneously. Thanks. >> >> Patch: http://people.freebsd.org/~gonzo/busdma.diff >> >> > > > > >