From owner-freebsd-arm@FreeBSD.ORG Mon Feb 11 00:40:00 2013 Return-Path: Delivered-To: freebsd-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 0672FBB0 for ; Mon, 11 Feb 2013 00:40:00 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id BFB2EADC for ; Mon, 11 Feb 2013 00:39:59 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r1B0do3G009260; Mon, 11 Feb 2013 00:39:50 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id sm3pzikzsjmystbzf4vpygwvqa; Mon, 11 Feb 2013 00:39:50 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: building RaspPi Images Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Tim Kientzle In-Reply-To: Date: Sun, 10 Feb 2013 16:39:49 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <1339E085-2B31-485D-9EED-9D0AFB7664C5@kientzle.com> References: <5116CB50.9080303@ceetonetechnology.com> <7757848F-45C6-4DEF-A4A2-5F900EB10A06@kientzle.com> <20130210012052.4d7e1a46@ivory.local> <58DCA6BE-8C06-4F69-81A2-A3582FBB5B12@kientzle.com> <8087503F-BE98-45B9-888B-044D9DA58B80@bsdimp.com> <20130210212025.009ee482@bender> To: Warner Losh X-Mailer: Apple Mail (2.1283) Cc: freebsd-arm@freebsd.org, Brett Wynkoop 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: Mon, 11 Feb 2013 00:40:00 -0000 On Feb 10, 2013, at 6:56 AM, Warner Losh wrote: >=20 > Right, we're doing it wrong. Or rather, we're using the standalone = interface when we should be using the linux interface. So you think that ubldr should startup like a Linux kernel? That's an interesting idea=85 Hmmmm=85.. > The stand alone interface should, in theory, provide us with the DTB, = but the code that is in ubldr doesn't seem to be reliably getitng this = image. I don't think anyone has spent time on this. We've just been focused on "making it work" and the compiled-in DTB does work for any single board. > uboot is supposed pass dtb to us. We're using the self-hosted = interface, rather than the linux interface, to boot. uboot is supposed = to have a jump table that we find and use to get the dtb from it, but = that code seems to not be working reliably. The interface works (I've spent a fair few hours fixing it), but I don't think anyone has tried getting the DTB from it. Any ideas for addressing the load-address problem? E.g., RPi has initial RAM mapped starting at address 0 and BeagleBone starts with RAM mapped to 0x80000000. Right now, that means we can't even share ubldr across those two systems because it has to be linked differently. > uboot gives linux images the DTB w/o any problem today, but you have = to run mkimage to get the image file to load into uboot for that to = work. Actually, the statement above isn't quite right for RPi. Linux on RPi doesn't use U-Boot. So we're currently using: RPi boot loader =3D> U-Boot =3D> ubldr =3D> kernel. The RPi boot loader does load the FDT and will pass it to a Linux kernel, but I don't think U-Boot implements that part of the linux kernel startup (which is why ubldr on RPi looks at a particular address in RAM to get the FDT from the RPi boot loader). Tim