From owner-freebsd-arm@FreeBSD.ORG  Thu Feb 28 23:36:02 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: arm@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id DA66BE15;
 Thu, 28 Feb 2013 23:36:02 +0000 (UTC) (envelope-from ray@freebsd.org)
Received: from smtp.dlink.ua (smtp.dlink.ua [193.138.187.146])
 by mx1.freebsd.org (Postfix) with ESMTP id 873AA95B;
 Thu, 28 Feb 2013 23:36:02 +0000 (UTC)
Received: from rnote.ddteam.net (12-60-135-95.pool.ukrtel.net [95.135.60.12])
 (Authenticated sender: ray)
 by smtp.dlink.ua (Postfix) with ESMTPSA id 35EB5C4930;
 Fri,  1 Mar 2013 01:36:01 +0200 (EET)
Date: Fri, 1 Mar 2013 01:35:45 +0200
From: Aleksandr Rybalko <ray@freebsd.org>
To: arm@FreeBSD.org, mips@freebsd.org, ppc@freebsd.org
Subject: [CFT + RFC] FDT resource management (patch)
Message-Id: <20130301013545.3d438d8e.ray@freebsd.org>
Organization: FreeBSD.ORG
X-Mailer: Sylpheed 3.1.2 (GTK+ 2.24.5; amd64-portbld-freebsd9.0)
X-Operating-System: FreeBSD
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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, 28 Feb 2013 23:36:02 -0000

Hi,

at first sorry for cross post, but IIRC we have no FDT list yet and I
don't want to break even single ppc/MPC85XX.

Now we have: fdtbus get physical address from the blob, map address
(panic on SPI CS "address" :) ) to virtual and return it as resource to
child bus (f.e. simplebus), but all other, not FDT based, ARCHes
delegate this work to parent of device who request resource. As result
we have virtual addresses in boot log + rman and it's try to map
address for not mapable buses.

Two month ago I made the patch:
http://people.freebsd.org/~ray/2012-12-25_fdt_correct_resource.diff
but testing give good results for i.MX515(Efika), BCM2835(RPi),
OMAPxxx(Pandaboard), but fail on Beagleboard.

Patch is simple, and I was surprised by BB problem, so I have to ask
help with testing on everything using fdtbus/simplebus.

Please help/test/comment! 

Many thanks!

WBW
-- 
Aleksandr Rybalko <ray@freebsd.org>