From owner-soc-status@FreeBSD.ORG Mon Aug 16 05:18:05 2010 Return-Path: Delivered-To: soc-status@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A6F41065674; Mon, 16 Aug 2010 05:18:05 +0000 (UTC) (envelope-from c.jayachandran@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8E83D8FC1D; Mon, 16 Aug 2010 05:18:04 +0000 (UTC) Received: by wwb24 with SMTP id 24so2876802wwb.31 for ; Sun, 15 Aug 2010 22:18:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/nTVUUT2hO8jjv8pQlGyxWbuiau6A9ORljkU6lL5V1s=; b=wJcfZPYw4LS7q1wfZnzalVBiMV/ycBtia97RHYdVpv+hH63j8hH9XHbtkxWyaXGuNU gqksQiuK1uaqayjtdZrUfKy34Jkz0n4ILTqA768JP9+RwBpxACKgIbsXMfcO+4Ssv1Ae cLthP0se91/BZtipVeuXKQbmI/+Qxv9VIP0Qk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=NLLtLGwnCNwMXEWp04Yp8J1B3edaCEIHlovDOo0+Oyi3+GtvFp3IboCtbsKjAsq6Ym xQAec57qHoPwPBx30i0aQ8rm42oaFUOs6Aj/kA+s7hJs1Fy/zGiVwEvrmN0IUAP9jXmT KH79oW1Yh5Hr6vUejxOtGQt1r587xHXvPV3aM= MIME-Version: 1.0 Received: by 10.216.181.6 with SMTP id k6mr2139186wem.42.1281934583505; Sun, 15 Aug 2010 21:56:23 -0700 (PDT) Received: by 10.216.160.10 with HTTP; Sun, 15 Aug 2010 21:56:23 -0700 (PDT) In-Reply-To: <4C67704C.70609@gmail.com> References: <4C67704C.70609@gmail.com> Date: Mon, 16 Aug 2010 10:26:23 +0530 Message-ID: From: "Jayachandran C." To: =?ISO-8859-7?Q?Vladimir_=27=F6=2Dcoder=2Fphcoder=27_Serbinenko?= Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: quoted-printable Cc: soc-status@freebsd.org, freebsd-mips@freebsd.org Subject: Re: Yeeloong port is functional X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Aug 2010 05:18:05 -0000 2010/8/15 Vladimir '=F6-coder/phcoder' Serbinenko : > Hello, all. Despite the hardware-inflicted setbacks (my yeeloong fried > right before the mid-term), Yeeloong port is now functional. Both serial > and local (keyboard + screen) work. Real Time Clock is working. Internet > is working. USB controller on PCI is working. Userspace is working. > > Remaining issues: > 1) Disabled cache. The reason are peculiar properties of L2 cache. I > actualy have the code to fix it but I'm not sure to hit GSoC deadline > about it. > 2) Only 256 MiB of RAM are supported. Should be easy to fix once 64-bit > parts are in. The 32bit kernel should support up to 4GB physical memory (we use 32bit physical address). More than 4GB is not still supported in 64 bit either. I am working on adding 64-bit page table entries, which will add this part. The only advantage on 64bit now is that we use XKPHYS to access memory above 512MB. > 3) No Geode support. So no IDE, 2 of 3 USB ports or audio. These > components are actualy pretty standard, one has only to add support for > MSRs. > 4) No power management. Wasn't planned to have it implemented during GSoC= . > > Not tested: > 1) Touchpad. Never connected to my laptop during developpement because > to use it one has to close front lid and so cut from serial connector > > 3rd party developpements =A0which will improve Yeeloong support: > 1) X.org support. The required card is already supported in latest > x.org. So it's a question of importing last X.org and testing it. > 2) 64-bit developpement. Currently if I compile 64-bit kernel it > contains only 64-bit imgact. Imposing only 64-bit binaries is suboptimal. Let me know if you find significant performance problems in the 64 bit code. I still haven't really tested the 64bit, so any reports will be useful JC.