From owner-freebsd-arm@FreeBSD.ORG Fri Jan 3 17:13:03 2014 Return-Path: Delivered-To: freebsd-arm@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 4C66BA5D; Fri, 3 Jan 2014 17:13:03 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1FAB51FCE; Fri, 3 Jan 2014 17:13:02 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Vz8Iq-000LNe-De; Fri, 03 Jan 2014 17:12:56 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s03HCsxA024096; Fri, 3 Jan 2014 10:12:54 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+0qgZjObqQudJIe2fpSeom Subject: Re: FreeBSD 10 on Dockstar (Marvell Kirkwood) From: Ian Lepore To: Nathan Whitehorn In-Reply-To: <52C35398.2090502@freebsd.org> References: <20131231211054.GA90299@moore.morphism.de> <52C35398.2090502@freebsd.org> Content-Type: text/plain; charset="us-ascii" Date: Fri, 03 Jan 2014 10:12:54 -0700 Message-ID: <1388769174.1158.269.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jan 2014 17:13:03 -0000 On Tue, 2013-12-31 at 18:30 -0500, Nathan Whitehorn wrote: > On 12/31/13 16:10, Markus Pfeiffer wrote: > > Hi all, > > > > I managed "fixing" it by editing the dockstar.dts file and putting for ranges: > > > > ranges = <0x0 0x2f 0xf9300000 0x00100000> > > > > Now I just have to figure out why this "fixes" it, and what damage that patch > > does. > > I also have some pathces for the LED on the dockstar which will tip up in my > > github soon. > > > > Cheers, > > markus > > Which node did you add this to? I'm trying to make our FDT code more > standards-compliant. This seems like something where we missed a spot. > -Nathan The surrounding context looks like this: localbus@f1000000 { #address-cells = <2>; #size-cells = <1>; compatible = "mrvl,lbc"; /* This reflects CPU decode windows setup. */ ranges = <0x0 0x0f 0xf9300000 0x00100000 0x1 0x1e 0xfa000000 0x00100000 0x2 0x1d 0xfa100000 0x02000000 0x3 0x1b 0xfc100000 0x00000400>; nor@0,0 { #address-cells = <1>; Specifying ranges here is a Marvel-SoC-specific thing, other arm socs don't require it. The Marvell code uses these values to set up hardware memory mapping; on the Marvell chips it's possible to map DRAM, NAND, PCIe, etc into physical address ranges of your choosing. -- Ian