From owner-freebsd-arm@FreeBSD.ORG  Fri May  2 09:01:29 2014
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
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 D2FE23EB;
 Fri,  2 May 2014 09:01:29 +0000 (UTC)
Received: from mail-ee0-x235.google.com (mail-ee0-x235.google.com
 [IPv6:2a00:1450:4013:c00::235])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 3847E1BFF;
 Fri,  2 May 2014 09:01:29 +0000 (UTC)
Received: by mail-ee0-f53.google.com with SMTP id b15so1785292eek.12
 for <multiple recipients>; Fri, 02 May 2014 02:01:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject
 :references:in-reply-to:content-type:content-transfer-encoding;
 bh=uJWth54i/7xBdV+XRqvwV4Cgv5tJ/1c5NPhRSSdVw9E=;
 b=MUF5jjfKZIixbiMJDdyu10PmYoi3lirq5IhUgOx893AA0SpdR8rTmftvtEK+IjFDqq
 c9pUKCy+P/XpXXFxKBcbI8j/TIg0p/8FbIwQK4G8rSKzu+Gp5/c1/4DdQtfu3+yxjZZj
 Vir44pmQSwI8hBFM0zHfPirGXX7wZaDD0M1tA6VaTLtlb6CkY4lYuKaMQskKA882/lX7
 51BSKsHzlhUcOAY9oeMiU3rmC5GrV4e8u9DXyjUVizFq9fH45ng6QfxQ7c047klunmYF
 nrW0Oanai+Ixt0LZjK+IPalaj2tOkhXV9fL4yxck8vyoCMUcJmARxqsAp2pkAZW8rVBn
 gLRQ==
X-Received: by 10.14.5.135 with SMTP id 7mr13832627eel.86.1399021287411;
 Fri, 02 May 2014 02:01:27 -0700 (PDT)
Received: from ketas-laptop.mydomain (ketas-laptop6.si.pri.ee.
 [2001:ad0:91f:0:21a:6bff:fe66:2ad3])
 by mx.google.com with ESMTPSA id bc51sm2995127eeb.22.2014.05.02.02.01.17
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Fri, 02 May 2014 02:01:25 -0700 (PDT)
Sender: Sulev-Madis Silber <madis555@gmail.com>
Message-ID: <53635ED5.6060508@hot.ee>
Date: Fri, 02 May 2014 12:01:09 +0300
From: "Sulev-Madis Silber (ketas)" <madis555@hot.ee>
User-Agent: Mozilla/5.0 (X11; FreeBSD i386;
 rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: Ian Lepore <ian@FreeBSD.org>
Subject: Re: FreeBSD-10-STABLE hangs when booting from BeagleBone Black eMMC
References: <CADH-AwHvaVqycykONkzRsj7oD3xSi8hszvc_Wf4obC=Y_qPiaQ@mail.gmail.com>
 <1398618984.61646.165.camel@revolution.hippie.lan>
 <CADH-AwE+5=A4aiqbTYqor1Any1JGNhz4LHOJwfyykYU92UpirQ@mail.gmail.com>
 <1398624759.61646.174.camel@revolution.hippie.lan>
 <CADH-AwG+saqXO4FYG65WMOuFyDzjbhF=a=-p3Y3En3zbcgyd6A@mail.gmail.com>
 <1398648505.61646.189.camel@revolution.hippie.lan>
 <CAD44qMX+hoeZ6yBD0v52xfoo5CXiUHgMz9qLa-=qhGYhhPUt1Q@mail.gmail.com>
 <CADH-AwEHRKSx11yjC5+kmYA4Q3Oh4VWpp-pr31eWwNc0bf0vUw@mail.gmail.com>
 <1398732508.61646.245.camel@revolution.hippie.lan>
 <CADH-AwHQjieXo-WgHkrc2wxwELwvrkg2spYucsZzRegvx9wWsA@mail.gmail.com>
 <1398784968.22079.13.camel@revolution.hippie.lan>
In-Reply-To: <1398784968.22079.13.camel@revolution.hippie.lan>
X-TagToolbar-Keys: D20140502120109841
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: FreeBSD ARM <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." <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: Fri, 02 May 2014 09:01:30 -0000

On 2014-04-29 18:22, Ian Lepore wrote:
> This may be the problem -- ubldr's behavior for finding and using dtb
> files is more complex than it used to be.  It may be that it used to
> claim to find and use the u-boot dtb, but it was really using a static
> dtb compiled into the kernel.  Now if u-boot provides a valid dtb it'll
> actually get used, even if kernel has a static dtb compiled in.
> 
> If you remove the u-boot env var 'fdtaddr' then it will fall back to
> using a compiled-in dtb file instead of a loaded one.
> 
> What I've been doing these days is installing my dtb files
> in /boot/modules or /boot/kernel and then setting the dtb file name in a
> u-boot env var named fdtfile.  That makes ubldr find and load the named
> file in the place it finds the kernel.
> 
> -- Ian


Nice, good suggestion. Now I have this "hack" in bb-uenv.txt:


------------------------------------------------------
uenvcmd=echo "[environment] delete fdtaddr"; env delete fdtaddr; setenv
loadfdt ''; setenv fdtfile "/boot/kernel/${fdtfile}"; echo
"[environment] loadfdt=${loadfdt}"; echo "[environment] fdtfile=${fdtfile}"
------------------------------------------------------


Not sure where FDT file should go? First I though maybe /boot/fdt...
then /boot/kernel seemed good place...


Also, maybe we should use this way of loading FDT in every platform it's
possible? No static FDT in kernel too. Ruins NFS boot, however...