From owner-freebsd-embedded@FreeBSD.ORG Mon Nov 25 22:17:27 2013 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CA8E6F3C; Mon, 25 Nov 2013 22:17:27 +0000 (UTC) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8DC9E2DE7; Mon, 25 Nov 2013 22:17:27 +0000 (UTC) Received: from vega.codepro.be (unknown [172.16.1.3]) by venus.codepro.be (Postfix) with ESMTP id 4CCBEFF53; Mon, 25 Nov 2013 23:17:26 +0100 (CET) Received: by vega.codepro.be (Postfix, from userid 1001) id 48CCBE29D; Mon, 25 Nov 2013 23:17:26 +0100 (CET) Date: Mon, 25 Nov 2013 23:17:26 +0100 From: Kristof Provost To: Ian Lepore Subject: Re: Incorrect struct onfi_params definition Message-ID: <20131125221726.GV58987@vega.codepro.be> References: <1383782353.31172.183.camel@revolution.hippie.lan> <1384381960-98851-1-git-send-email-kristof@sigsegv.be> <1384537153.31172.398.camel@revolution.hippie.lan> <20131115191315.GF58987@vega.codepro.be> <1384544870.31172.420.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1384544870.31172.420.camel@revolution.hippie.lan> X-PGP-Fingerprint: E114 D9EA 909E D469 8F57 17A5 7D15 91C6 9EFA F286 User-Agent: Mutt/1.5.22 (2013-10-16) 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: Mon, 25 Nov 2013 22:17:27 -0000 On 2013-11-15 12:47:50 (-0700), Ian Lepore wrote: > Is it only the parameter-read that has this problem, or do regular reads > and writes fail to get status too? Maybe there's something in the > marvell nand flash interface that leads to this; I did my work on an > Atmel SoC (but I do have a Dreamplug here that has nand flash on it, > it's sort of a Guruplug in a Dreamplug case; not many were shipped). > It's only the parameter-read. Regular reads do not time out. I've managed to format the flash with nandfs and can now read/write it normally. Regards, Kristof