From owner-freebsd-arm@FreeBSD.ORG  Thu Feb  5 19:04:26 2009
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
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 43970106568A;
	Thu,  5 Feb 2009 19:04:26 +0000 (UTC)
	(envelope-from avinogradovs@clearpathnet.com)
Received: from hosting.clearpathnet.com (hosting.clearpathnet.com
	[74.217.144.9])
	by mx1.freebsd.org (Postfix) with ESMTP id 11B138FC13;
	Thu,  5 Feb 2009 19:04:25 +0000 (UTC)
	(envelope-from avinogradovs@clearpathnet.com)
Received: from [10.1.16.109] (la-209-182-100-49 [209.182.100.49] (may be
	forged)) by hosting.clearpathnet.com (8.13.1/8.13.1) with ESMTP id
	n15J4I7H020552; Thu, 5 Feb 2009 11:04:21 -0800
Message-ID: <498B3874.2020902@clearpathnet.com>
Date: Thu, 05 Feb 2009 11:05:24 -0800
From: Alex Vinogradovs <avinogradovs@clearpathnet.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080915)
MIME-Version: 1.0
To: Sam Leffler <sam@freebsd.org>
References: <498B32B0.1050306@clearpathnet.com> <498B36CD.3010402@freebsd.org>
In-Reply-To: <498B36CD.3010402@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-arm@freebsd.org
Subject: Re: cfi causes vm_fault on IXP435
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
	<mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
	<mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2009 19:04:27 -0000

No worries, I am just testing the things out. This board in particular 
has been customized for my company, so
I was just wondering if it would work without hacking the kernel ;)

Alex.


Sam Leffler wrote:
> Well I didn't enable it for Cambria because it wasn't right :-)
>
> I know that at the very least the flash config on the 2358 is 32M but 
> I only map 16M so if everything else worked you couldn't access all 
> the memory.  But otherwise I hit this fault and haven't had time to 
> diagnose it.  Not sure when I'll get to it; would love to have some 
> help (once you get it mapped correctly you can add support to the cfi 
> driver to dynamically map 1M blocks so we don't have to map all of 
> flash).
>
> BTW since you tried this w/o asking you probably noticed I also just 
> committed support for the SrataFlash protection register.  It looks 
> like it might be working and I was just confused about the ability to 
> write the user segment multiple times.  The doc is a bit confusing and 
> seems to say this 64-bit segment is OTP (write once).  I think I need 
> to move the code that lets you write it under the CFI_AMEDANDDANGEROUS 
> option...
>
>    Sam
>