announcing the availability of packages for the Arm architecture

[Adrian Chadd]

On 6 November 2012 08:43, Warner Losh <imp at 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