Date: Fri, 15 Nov 2013 10:39:13 -0700 From: Ian Lepore <ian@FreeBSD.org> To: kristof@sigsegv.be Cc: Grzegorz Bernacki <gber@FreeBSD.org>, freebsd-embedded@FreeBSD.org Subject: Re: Incorrect struct onfi_params definition Message-ID: <1384537153.31172.398.camel@revolution.hippie.lan> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1384537153.31172.398.camel>