From owner-freebsd-arm@FreeBSD.ORG Thu Feb 21 14:58:44 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1B29D88B for ; Thu, 21 Feb 2013 14:58:44 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ia0-x22c.google.com (ia-in-x022c.1e100.net [IPv6:2607:f8b0:4001:c02::22c]) by mx1.freebsd.org (Postfix) with ESMTP id E0720A9A for ; Thu, 21 Feb 2013 14:58:43 +0000 (UTC) Received: by mail-ia0-f172.google.com with SMTP id l29so6149141iag.17 for ; Thu, 21 Feb 2013 06:58:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer:x-gm-message-state; bh=70/kVyayxlgxprR+Rz/pDaNH4jZ4zYq25YdYEedX3xQ=; b=JzekeinSci5i+3sDnalMZXD+91138Mjpn+M3laGpKkGsKA0i0KqdMQKyriSGH+po0r jM4V0q1baTLww1fsW98k0RAc6xbLBQGlmmfLE2t1H9ZNRyIAY53F/l6GYbqItXN4acoA kpX3I2rBNIJ13Vizhw2GDZklu4z0GuSAueFbKBhwmFhGHUhAVhP3UIv5dh4751WEMAN5 XUlucCr4h057LEBZChIw8T481BGgsHCtmd18GbuPJeRSGa2NGQcm3KnlBFeu28NA4Lr1 kaiw1OuHEtzBXgg/dyuykgiuclc6ypy2h0W/yxkNHuiePPwzwG383Y+qqMoXIJnOeZ6m BN6w== X-Received: by 10.50.88.168 with SMTP id bh8mr4049256igb.67.1361458723413; Thu, 21 Feb 2013 06:58:43 -0800 (PST) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id dy5sm12385494igc.1.2013.02.21.06.58.41 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Feb 2013 06:58:42 -0800 (PST) Sender: Warner Losh Subject: Re: The Next BeagleBone Better & Faster for Less! Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <1361458105.1185.19.camel@revolution.hippie.lan> Date: Thu, 21 Feb 2013 07:58:40 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <5125A73F.10802@ceetonetechnology.com> <20130221011346.3c376117@ivory.wynn.com> <48679DB0-7A2B-4617-BAA3-30C21F3CD61B@bsdimp.com> <1361458105.1185.19.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQmzDBavKylRer3xaa03YnFwCb0kl8shZPx1MfPqqqqeNnKiS6N3ZNJRKG1VRJxrbUuXAFQ/ Cc: george@ceetonetechnology.com, freebsd-arm@FreeBSD.org, Brett Wynkoop X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2013 14:58:44 -0000 On Feb 21, 2013, at 7:48 AM, Ian Lepore wrote: > On Wed, 2013-02-20 at 23:49 -0700, Warner Losh wrote: >> On Feb 20, 2013, at 11:13 PM, Brett Wynkoop wrote: >>=20 >>> On Wed, 20 Feb 2013 23:49:03 -0500 >>> George Rosamond wrote: >>>=20 >>>> On 02/20/13 23:27, Alie Tan wrote: >>>>> Just got a news about new Beaglebone: >>>>>=20 >>>>> http://beagleboard.org/unzipped/ >>>>=20 >>>> Wow. Although personally, I could do without the HDMI. >>>>=20 >>>> It would be ideal there was a stock FBSD image for them to provide = for >>>> purchasers... as in official on their www site as an alternative to >>>> Linux. >>>>=20 >>>> g >>>=20 >>> Greeting- >>>=20 >>> We need working USB support to contribute that to their site. >>>=20 >>> Is this new bone going to be the same as the old bone, but with = video, >>> in other words will current kernels run or will the hard core kernel >>> folks have to rework things? >>=20 >> We'll likely have to rework thing, at least if we want to run out of = flash on the card. it has a new flash chip that has micron markings on = it. Sure would be nice to know what, exactly, that chip is... >>=20 >> Warner >=20 > Unless it's a fairly old chip, or one of Micron's offerings with = on-chip > ECC, our current ecc code isn't going to handle it. I just spent = weeks > learning that the hard way. The ecc code we have checked in is a > hamming code implementation that can correct single-bit errors, and > modern nand chips are requiring algorithms that can correct multi-bit > errors. Our current code also isn't ready to handle the situation = where > the SoC's nand flash controller hardware does ecc with some = cooperation > from software. Yes. I believe that the newest ~20nm chips require 40 bits per 1k of = correction, and the current, but soon to be phased out ~25nm chips = require 30 bits of correction. Only the really old 5x nm MLC parts and = up through the 3x SLC parts can get bye with a 1 bit corrector. Most = people use some flavor of bch code these days, not the simpler hamming = code. I'm not aware of any NAND chips that have the ECC engine integrated into = them, but that may just be due to my focus in the NAND market these = days. Are you sure you don't mean ECC engines in the SoC itself, which = seem to be much more common? Then again, I've been trying to avoid = dealing too much with NAND Flash in open source these days... Warner=