From owner-freebsd-arm@FreeBSD.ORG Thu Jun 21 09:52:12 2012 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5F0010657DE; Thu, 21 Jun 2012 09:52:12 +0000 (UTC) (envelope-from kp@sigsegv.be) Received: from mercury.codepro.be (mercury.codepro.be [IPv6:2001:4b98:dc0:51:216:3eff:feb7:3147]) by mx1.freebsd.org (Postfix) with ESMTP id 77E988FC16; Thu, 21 Jun 2012 09:52:12 +0000 (UTC) Received: from adrastea.jupiter.sigsegv.be (adrastea.jupiter.sigsegv.be [IPv6:2001:6f8:1498:1::3]) by mercury.codepro.be (Postfix) with ESMTP id 5FC4311C; Thu, 21 Jun 2012 11:52:11 +0200 (CEST) Received: from thebe.jupiter.sigsegv.be (thebe.jupiter.sigsegv.be [172.16.1.5]) by adrastea.jupiter.sigsegv.be (Postfix) with ESMTP id 2AD811CF6; Thu, 21 Jun 2012 11:52:11 +0200 (CEST) Received: by thebe.jupiter.sigsegv.be (Postfix, from userid 1000) id 09BDE156C6; Thu, 21 Jun 2012 11:52:10 +0200 (CEST) Date: Thu, 21 Jun 2012 11:52:10 +0200 From: Kristof Provost To: Alexander Motin Message-ID: <20120621095210.GK9423@thebe.jupiter.sigsegv.be> References: <4FE2EDBA.1030505@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4FE2EDBA.1030505@FreeBSD.org> X-PGP-Fingerprint: E114 D9EA 909E D469 8F57 17A5 7D15 91C6 9EFA F286 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-arm@FreeBSD.org Subject: Re: Cache write-back issue on Marvell SoC (SheevaPlug) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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 Jun 2012 09:52:13 -0000 On 2012-06-21 12:47:38 (+0300), Alexander Motin wrote: > Unluckily I have no idea in arm assembler and cache control > interfaces. Could somebody recheck existing D-cache range write-back > code, because there seems to be a problem? > There's a general problem with the Kirkwood (and possibly other chips, I don't know) in that area. I've run into similar problems on my OpenRD, using a USB stick. There's a little more information in arm/158950. Regards, Kristof