From owner-freebsd-embedded@FreeBSD.ORG Fri Nov 15 17:39:23 2013 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0CF211DF; Fri, 15 Nov 2013 17:39:23 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D88612991; Fri, 15 Nov 2013 17:39:22 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VhNMS-000K3H-DO; Fri, 15 Nov 2013 17:39:16 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id rAFHdDOY075132; Fri, 15 Nov 2013 10:39:13 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+3kgq9+V21qC5JqD35dOB/ Subject: Re: Incorrect struct onfi_params definition From: Ian Lepore To: kristof@sigsegv.be In-Reply-To: <1384381960-98851-1-git-send-email-kristof@sigsegv.be> References: <1383782353.31172.183.camel@revolution.hippie.lan> <1384381960-98851-1-git-send-email-kristof@sigsegv.be> Content-Type: text/plain; charset="us-ascii" Date: Fri, 15 Nov 2013 10:39:13 -0700 Message-ID: <1384537153.31172.398.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Grzegorz Bernacki , freebsd-embedded@FreeBSD.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2013 17:39:23 -0000 On Wed, 2013-11-13 at 23:32 +0100, kristof@sigsegv.be wrote: > Hi Ian, > > Here's my attempt at a cleaned up patch series. > > It doesn't include the delay modifications from your nand2.diff, as that > didn't actually work for me. On my OpenRD is appears that the time tick is > started after the NAND initialisation, leading to infinite delays. > I'm interested in hearing more about this. I don't quite understand what you mean by "time tick is started after...". The delay-related changes should completely remove all use of clocks or timing. What it does instead is repeatedly issue "get status" commands to the chip until the chip says it's done with the previous operation and ready to continue. The big advantage is that a DELAY(1000) will always wait a millisecond, but modern nand chips are often ready to procede after just a few microseconds. It really helped bulk data throughput. -- Ian