Date: Sat, 9 Feb 2013 23:18:03 -0800 From: Tim Kientzle <tim@kientzle.com> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-arm@freebsd.org, Brett Wynkoop <wynkoop@wynn.com> Subject: Re: building RaspPi Images Message-ID: <EB4A0D67-9813-47DA-B3DB-F1309B2773F5@kientzle.com> In-Reply-To: <E691571B-EA19-4485-BB02-7486685B44C7@bsdimp.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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 9, 2013, at 11:07 PM, Warner Losh wrote: >> * 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? 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. 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. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EB4A0D67-9813-47DA-B3DB-F1309B2773F5>