Date: Tue, 6 Nov 2012 11:21:09 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: Tim Kientzle <tim@kientzle.com>, freebsd-arm@freebsd.org Subject: Re: announcing the availability of packages for the Arm architecture Message-ID: <CAJ-Vmo=tf1sucY5S%2BofJFEvCoR1PP0569=0LxZJK9EOM05%2BS_Q@mail.gmail.com> In-Reply-To: <7D9E09AD-95C6-4DD5-9D47-9A04D950DB36@bsdimp.com> References: <CANuCnH_pKuUPhYe-AQ6MpK_XXPSdpft5zhQzEjFBSpfWAPRqKA@mail.gmail.com> <1351606727.1120.17.camel@revolution.hippie.lan> <5097263F.5090802@jetcafe.org> <1D4ECD72-D01D-48D3-B837-735176CC49D3@kientzle.com> <50983301.9040406@jetcafe.org> <162A6F5A-8CC4-44DE-9B46-D9D6D8CC00CE@kientzle.com> <7D9E09AD-95C6-4DD5-9D47-9A04D950DB36@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 November 2012 08:43, Warner Losh <imp@bsdimp.com> wrote: >> The key piece right now is a concept of "board" that >> encapsulates how to partition a disk image for a >> particular system and what boot bits it requires. > > I'd love to see a bigger framework akin to NanoBSD that allows one to mix in the application with the board to produce an image customized for your needs. zrouter does this a bit, as does Tim's scripts, but we aren't quite to where we need to be. So question #1: do we import those firmware image tools into /usr/src/contrib/, or do we just require that building these things requires certain ports to be installed? I don't mind wrapping up my build binaries into ports (ie, mkuboot stuff with the right mklzma, mktplinkfw, mkubnt) and beginning the process of merging stuff into -HEAD. ARM is a bit more convoluted as there's sometimes a bootloader and bootblocks involved. Thanks, Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=tf1sucY5S%2BofJFEvCoR1PP0569=0LxZJK9EOM05%2BS_Q>