Date: Thu, 24 May 2012 09:01:19 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Damjan Marion <dmarion@freebsd.org> Cc: arm@freebsd.org, Adrian Chadd <adrian@freebsd.org>, freebsd-current FreeBSD <freebsd-current@freebsd.org> Subject: Re: Customizing ubldr build... Message-ID: <20E4AEBE-C847-450C-8469-A216DD5B6989@freebsd.org> In-Reply-To: <B9008F20-E417-48BC-AAAC-8111A39B0A8B@FreeBSD.org> References: <E84EA543-11A9-4EA6-9313-6908F485C569@freebsd.org> <CAJ-VmomyYPzqEJ86a6tfKSDeYrBqD21UDjefqyFNZC4yJ-pLWA@mail.gmail.com> <EBC5FF24-B1F5-43CD-AB1C-3BB659E8F5C6@freebsd.org> <B9008F20-E417-48BC-AAAC-8111A39B0A8B@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 24, 2012, at 1:16 AM, Damjan Marion wrote: > On May 24, 2012, at 6:35 AM, Tim Kientzle wrote: >=20 >> I think the PandaBoard ES is fully supported by U-Boot, >> so it should be possible to use ubldr as part of the boot >> chain for that just like I've been doing with BeagleBone. >=20 > What are the benefits of using ubldr compared to what we are doing = today(load; go)? For a fully custom closed embedded system, nothing. But as we move towards more generic kernels that support more environments, ubldr has the ability to: * Load the kernel from UFS (which in turn means that end users can use = buildkernel/installkernel to update the kernel) * Load the device tree separately from the kernel. * Interactively edit the device tree * Preload specific modules * Script the boot process (the i386 interactive boot menu is a Forth = script that runs on the stock loader; ubldr has the same ability) Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20E4AEBE-C847-450C-8469-A216DD5B6989>