Date: Wed, 20 Feb 2013 09:49:59 -0700 From: Warner Losh <imp@bsdimp.com> To: Tim Kientzle <kientzle@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: No more compiled-in FDTs?! Message-ID: <D7781B88-B8DB-4C63-AAAA-DE658126637E@bsdimp.com> In-Reply-To: <726FA1B6-C3D7-479B-A6E0-78E8CC49144A@freebsd.org> References: <726FA1B6-C3D7-479B-A6E0-78E8CC49144A@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 20, 2013, at 9:44 AM, Tim Kientzle wrote: > I've just committed changes so that BeagleBone images > (built with my scripts) no longer use the compiled-in FDT. > (This includes changes to FreeBSD ubldr, to U-Boot, > and to my scripts.) > > RaspberryPi has not been using the compiled-in FDT for > some time now. > > My goal is demonstrate booting a single kernel on > multiple ARM boards, which necessarily precludes > using a compiled-in FDT. > > I plan to soon comment-out the compiled-in FDT from > the kernel configurations in FreeBSD SVN for both > BeagleBone and RaspberryPi. > > For reference, you can load an FDT from U-Boot: > $ fatload mmc 0:1 <address> <filename.dtb> > $ fdt addr <address> > > or from within ubldr: > $ load -t fdt <filename.dtb> > > These commands can be easily automated. In either > case, ubldr should now find the FDT and correctly pass > it to the kernel. That's awesome. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D7781B88-B8DB-4C63-AAAA-DE658126637E>