Date: Sun, 10 Feb 2013 00:47:38 -0700 From: Warner Losh <imp@bsdimp.com> To: Tim Kientzle <tim@kientzle.com> Cc: freebsd-arm@freebsd.org, Brett Wynkoop <wynkoop@wynn.com> Subject: Re: building RaspPi Images Message-ID: <8087503F-BE98-45B9-888B-044D9DA58B80@bsdimp.com> In-Reply-To: <EB4A0D67-9813-47DA-B3DB-F1309B2773F5@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> <E691571B-EA19-4485-BB02-7486685B44C7@bsdimp.com> <EB4A0D67-9813-47DA-B3DB-F1309B2773F5@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 10, 2013, at 12:18 AM, Tim Kientzle wrote: > On Feb 9, 2013, at 11:07 PM, Warner Losh wrote: >=20 >>> * For RPi, this already happens: the first-stage boot >>> loads a DTB, ubldr uses "fdt addr" to access that DTB >>> in a known location and then passes it to the kernel. >>=20 >> Doesn't the RPi's boot loader give our /boot/loader enough info to = get this without the fdt addr command? >=20 > I haven't dug into this yet, but there's a mismatch somewhere > between the RPi first-stage boot loader, U-Boot, and our ubldr. >=20 > I briefly tried loading our kernel straight from the RPi > first stage boot loader (dropping U-Boot and ubldr > phases) but didn't get very far with it. Our ubldr currently ignores r2 on boot, and tries to get the FDT via a = different uboot interface, but I'm thinking that part is broken...=20 Warner=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8087503F-BE98-45B9-888B-044D9DA58B80>