From owner-freebsd-arm@FreeBSD.ORG Wed Jan 9 23:27:41 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 F37FC3A2 for ; Wed, 9 Jan 2013 23:27:40 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (moon.peach.ne.jp [203.141.148.98]) by mx1.freebsd.org (Postfix) with ESMTP id A881734B for ; Wed, 9 Jan 2013 23:27:40 +0000 (UTC) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id 4208B39E09; Thu, 10 Jan 2013 08:27:38 +0900 (JST) Received: from artemis (unknown [172.18.0.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTPSA id 2CA9139D62; Thu, 10 Jan 2013 08:27:38 +0900 (JST) Message-ID: <2D3E891FE9014C0B8403E27EBAFC9EF9@ad.peach.ne.jp> From: "Daisuke Aoyama" To: "Oleksandr Tymoshenko" , References: <2659960079254C38ACD2F1DCBB7A1A19@ad.peach.ne.jp> <50EDF4AB.5060606@bluezbox.com> In-Reply-To: <50EDF4AB.5060606@bluezbox.com> Subject: Re: FreeBSD/armv6z/clang on Raspberry Pi 512MB (with U-Boot + ubldr) Date: Thu, 10 Jan 2013 08:27:34 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP 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: Wed, 09 Jan 2013 23:27:41 -0000 >> Known Problems: >> To store correct values to DMA engine, it uses D-cache invalidate all. >> (unknown reason, first chunk only) > > Thank you, Daisuke-san. I'm going to merge DMA driver and DMA transfers > support for SDHCI. Merging other SDHCI fixes require more testing (and > spec reading) > but they're on my ToDo list too. DMA driver needs some clean-up though > before it can be committed to the tree. I'll post my notes on it when > it's ready. I forgot invalidating SDHCI side. I've fixed this issues. Please take from src-244906-20130110.patch.gz and new bcm2835_dma.[ch]. (dated 2013/Jan/10) So, now it should take invalidate range correctly instead of D-cache invalidate all. FYI, my patch fix: wrong high voltage selection in dev/mmc/mmc.c workaround missing error handling in dev/mmc/mmc.c wrong freq divider in dev/sdhci/sdhci.c workaround Raspberry Pi HS mode issue in dev/sdhci/sdhci.c Thanks, -- Daisuke Aoyama