From owner-freebsd-arm@FreeBSD.ORG Wed Nov 28 22:24:28 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 351F6CF9 for ; Wed, 28 Nov 2012 22:24:28 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id CD0C98FC0C for ; Wed, 28 Nov 2012 22:24:27 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fo13so19112453vcb.13 for ; Wed, 28 Nov 2012 14:24:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=YE5/Qlf+GBpLOeJWgcuZ9nWf+sHKrqTwMTs1+wWTph0=; b=ND98/YPGtyN0IbAzd8iwVoNG39mNiLHOldPUVPLW/kkWlOVJvViB13KG5RFVCnoY4k JA4WHbZXOZZDvZkXCfkVAX1LWUktZSZ16z2RmRvjTQKVnuBu7GAEIxNfYDB3VISDaLss 2LMQ4yFfQ409AvFFHE59rzkBtASADfz4hb4AnKZH8iKz8W88sJuzQlPLeMFi/DFXqM77 d5TUThU02Izniz11YtnUeKjR2PfkK7Dz4iViIE29jDRa7RFSzp0FwFl5bOBOKB+9etRA eB2xBAobEEGHXzh7aLG4R7jqyS7yJcK21jxKoMRVTdcFHB4ae0+LOso+oKW5J4bi9FEx Oeaw== Received: by 10.52.98.67 with SMTP id eg3mr1489272vdb.59.1354141466634; Wed, 28 Nov 2012 14:24:26 -0800 (PST) Received: from [10.30.101.53] ([209.117.142.2]) by mx.google.com with ESMTPS id co1sm12177127vdc.10.2012.11.28.14.24.23 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Nov 2012 14:24:25 -0800 (PST) Sender: Warner Losh Subject: Re: FDT code fixes for ubldr Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <50B68CFA.80208@bluezbox.com> Date: Wed, 28 Nov 2012 15:24:21 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <50B54AB7.8080301@bluezbox.com> <50B68CFA.80208@bluezbox.com> To: Oleksandr Tymoshenko X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQn1kYZ/0poCcKfLs+AcBNbtX/2naeCw+cS0as8F6mrQ4L2eSrHkzn9cQaaWFlg7ymC3nOUY Cc: arm@freebsd.org, embedded@freebsd.org, Tim Kientzle 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, 28 Nov 2012 22:24:28 -0000 On Nov 28, 2012, at 3:15 PM, Oleksandr Tymoshenko wrote: > On 11/27/2012 3:20 PM, Oleksandr Tymoshenko wrote: >> Hi guys, >>=20 >> Here is a patch for FDT support in ubldr: >> http://people.freebsd.org/~gonzo/patches/fdt.diff >> Reviews are appreciated >>=20 >> I also plan to add merge of memreserve and memory regions as a part = of memory fixup process. >>=20 >> Changes: >> - Implement "fdt mres" sub-command that prints reserved memory = regions >> - Add "fdt addr" subcommand that lets you specify preloaded blob = address >> - Do not pre-initialize blob for "fdt addr" >> - Do not try to load dtb every time fdt subcommand is issued, >> do it only once >> - Change the way DTB is passed to kernel. With introduction of "fdt = addr" >> actual blob address can be not virtual but physical or reside in >> area higher then 64Mb. ubldr should create copy of it in kernel = area >> and pass pointer to this newly allocated buffer which is = guaranteed to work >> in kernel after switching on MMU. >>=20 >=20 > New version of this patch: > http://people.freebsd.org/~gonzo/patches/fdt-memreserve.diff >=20 > Additional changes: >=20 > - Convert memreserv FDT info to memreserv property of root node > - Handle memreserv property in initarm: exclude these regions from = available memory regions >=20 > With these changes I was able to boot Raspberry Pi with all = hardware-specific data set correctly by firmware. > If there are not objections, I'd like to commit it ASAP. Nothing horrible is leaping out at me. Please do. On a related note: any plans to have the ability to merge new = nodes/change nodes from the loader? I know this doesn't make sense in = the NAND environment so much, but makes a lot more sense for the SD = environment when you may wish to monkey with the command line, or = disable devices, or even load a set of nodes that describe some new = custom hardware, perhaps conditionally... Warner