Remove the "cubie" miniroot. There are far more popular armv7 boards
with Allwinner SoCs and the presence of this particular miniroot is making
it hard to update U-Boot.

ok jsg@

adapt to new dir layout in dtb packages; ok deraadt

Change variable 'DISKTYPE' to 'FSDISKTYPE' like every other arch.

No functional change.

ok patrick@

Use "echo '/ *' | disklabel -wAT-" to put all free space into the
root partition.

Identical behaviour as but more readable than the "echo 'a
a\n\n\n\nw\nq\n'| disklabel -E" it replaces.

It also eliminates the extraneous output of -E that required
">/dev/null".

ok kn@

Use fdisk's -b to create boot partitions instead of -e scripts.

Build, boot and install tested by visa@

ok visa@

make armv7 fit again after bootblock growth; discussed with jsg

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

When writing to a raw vnd device with dd if the input file size is not a
multiple of bs use conv=sync to zero pad the final record. Avoids
"vnd0: sloppy write from proc" messages when building arm releases.

tested by deraadt@

Change the offset filesystems start on disk for armv7 from 1MB to 16MB.
Matches arm64 and is required for rk3288 with TPL now U-Boot is expected
to be found at sector 16384 (8MB).

ok kettenis@ patrick@

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

adapt to new dir layout in dtb packages; ok deraadt

Change variable 'DISKTYPE' to 'FSDISKTYPE' like every other arch.

No functional change.

ok patrick@

Use "echo '/ *' | disklabel -wAT-" to put all free space into the
root partition.

Identical behaviour as but more readable than the "echo 'a
a\n\n\n\nw\nq\n'| disklabel -E" it replaces.

It also eliminates the extraneous output of -E that required
">/dev/null".

ok kn@

Use fdisk's -b to create boot partitions instead of -e scripts.

Build, boot and install tested by visa@

ok visa@

make armv7 fit again after bootblock growth; discussed with jsg

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

When writing to a raw vnd device with dd if the input file size is not a
multiple of bs use conv=sync to zero pad the final record. Avoids
"vnd0: sloppy write from proc" messages when building arm releases.

tested by deraadt@

Change the offset filesystems start on disk for armv7 from 1MB to 16MB.
Matches arm64 and is required for rk3288 with TPL now U-Boot is expected
to be found at sector 16384 (8MB).

ok kettenis@ patrick@

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

Change variable 'DISKTYPE' to 'FSDISKTYPE' like every other arch.

No functional change.

ok patrick@

Use "echo '/ *' | disklabel -wAT-" to put all free space into the
root partition.

Identical behaviour as but more readable than the "echo 'a
a\n\n\n\nw\nq\n'| disklabel -E" it replaces.

It also eliminates the extraneous output of -E that required
">/dev/null".

ok kn@

Use fdisk's -b to create boot partitions instead of -e scripts.

Build, boot and install tested by visa@

ok visa@

make armv7 fit again after bootblock growth; discussed with jsg

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

When writing to a raw vnd device with dd if the input file size is not a
multiple of bs use conv=sync to zero pad the final record. Avoids
"vnd0: sloppy write from proc" messages when building arm releases.

tested by deraadt@

Change the offset filesystems start on disk for armv7 from 1MB to 16MB.
Matches arm64 and is required for rk3288 with TPL now U-Boot is expected
to be found at sector 16384 (8MB).

ok kettenis@ patrick@

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

Use "echo '/ *' | disklabel -wAT-" to put all free space into the
root partition.

Identical behaviour as but more readable than the "echo 'a
a\n\n\n\nw\nq\n'| disklabel -E" it replaces.

It also eliminates the extraneous output of -E that required
">/dev/null".

ok kn@

Use fdisk's -b to create boot partitions instead of -e scripts.

Build, boot and install tested by visa@

ok visa@

make armv7 fit again after bootblock growth; discussed with jsg

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

When writing to a raw vnd device with dd if the input file size is not a
multiple of bs use conv=sync to zero pad the final record. Avoids
"vnd0: sloppy write from proc" messages when building arm releases.

tested by deraadt@

Change the offset filesystems start on disk for armv7 from 1MB to 16MB.
Matches arm64 and is required for rk3288 with TPL now U-Boot is expected
to be found at sector 16384 (8MB).

ok kettenis@ patrick@

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

Use fdisk's -b to create boot partitions instead of -e scripts.

Build, boot and install tested by visa@

ok visa@

make armv7 fit again after bootblock growth; discussed with jsg

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

When writing to a raw vnd device with dd if the input file size is not a
multiple of bs use conv=sync to zero pad the final record. Avoids
"vnd0: sloppy write from proc" messages when building arm releases.

tested by deraadt@

Change the offset filesystems start on disk for armv7 from 1MB to 16MB.
Matches arm64 and is required for rk3288 with TPL now U-Boot is expected
to be found at sector 16384 (8MB).

ok kettenis@ patrick@

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

make armv7 fit again after bootblock growth; discussed with jsg

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

When writing to a raw vnd device with dd if the input file size is not a
multiple of bs use conv=sync to zero pad the final record. Avoids
"vnd0: sloppy write from proc" messages when building arm releases.

tested by deraadt@

Change the offset filesystems start on disk for armv7 from 1MB to 16MB.
Matches arm64 and is required for rk3288 with TPL now U-Boot is expected
to be found at sector 16384 (8MB).

ok kettenis@ patrick@

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

Make ffs2 the default for newfs; change all calls to create e.g. floppy
filesystems or ramdisks to use explicit -O 1; installer already does that.
ok sthen@

Change install images called *.fs to *.img. These are UFS filesystem images,
but additionally have a bootblock in the first 8K (since UFS does not use that
space). There are some UEFI direct-from-internet bootloaders that require
the name *.img. So this makes things more convenient for those, while keeping
it consistant in all architectures.
ok kettenis beck kn

When writing to a raw vnd device with dd if the input file size is not a
multiple of bs use conv=sync to zero pad the final record. Avoids
"vnd0: sloppy write from proc" messages when building arm releases.

tested by deraadt@

Change the offset filesystems start on disk for armv7 from 1MB to 16MB.
Matches arm64 and is required for rk3288 with TPL now U-Boot is expected
to be found at sector 16384 (8MB).

ok kettenis@ patrick@

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

When writing to a raw vnd device with dd if the input file size is not a
multiple of bs use conv=sync to zero pad the final record. Avoids
"vnd0: sloppy write from proc" messages when building arm releases.

tested by deraadt@

Change the offset filesystems start on disk for armv7 from 1MB to 16MB.
Matches arm64 and is required for rk3288 with TPL now U-Boot is expected
to be found at sector 16384 (8MB).

ok kettenis@ patrick@

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

Change the offset filesystems start on disk for armv7 from 1MB to 16MB.
Matches arm64 and is required for rk3288 with TPL now U-Boot is expected
to be found at sector 16384 (8MB).

ok kettenis@ patrick@

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

Further removal of differences (using install instead of cp, sorting
chunks in a specified order, using a few variables, performing bsd.rd
to bsd.gz conversion as similar as possible)

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

Every Makefile on every architecture had deviated in unique ways.
Eliminate many more differences. When it makes sense, build bsd.rd
and miniroot/ramdisk.fs and cd.iso in the same directory. More steps
coming after this..

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

remove the abstraction REV on top of abstraction OSrev which is always
the sme.

Use new vnconfig vnd-auto-allocate mode. Resolve some variation between
architectures, and start removing some crazy junk that has collected
over the years. Being tested on all architectures...
ok various people.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.

Mainline u-boot on SABRE Lite/BD-SL-i.MX6 does not have the generic
distro hooks that automatically load an efi file if found.

Instead it looks for a '6x_bootscript' u-boot script as the original
boundary devices u-boot did.

Create a script in the nitrogen miniroot and on install that will
load a dtb and bootarm.efi then call bootefi. Based on notes
from matthieu@

Previously armv7 ramdisk creation would tar up the mdec directory on the
build machine and extract it when installing. Change to using the
u-boot and dtb packages when creating ramdisks and miniroots and don't
place these files in mdec on install.

Installing these packages is now required to run make release on armv7.

Add back the fdisk command to flag the fat fs as active.
The omap boot rom that loads the first u-boot stage requires this.

Assume sabrelite/nitrogen has a bootefi enabled u-boot in flash and just
install dtbs and efiboot on the fat fs.

use efiboot in armv7 miniroot images

Use a fat16 partition starting at sector 2048/1MB everywhere to simplify
things. OMAP can still load the first u-boot stage (MLO) from the fs
and imx u-boot can load files off fat. The offset allows space for the
u-boot images placed at raw offsets on imx and sunxi.

discussed with kettenis

use a simple u-boot script for all the miniroots that loads with fdt
ok patrick@ kettenis@

Copy dtb files to miniroots and install disk. Increase the ramdisk size
and force long filenames on the first mount of fat 16 filesystems so
this works.

U-boot scripts have not yet been changed to load these files.

ok kettenis@

Switch from the solidrun i.mx6 u-boot to mainline u-boot on cubox i.
The offset of u-boot.img in the disk image changes to be the same as
wandboard.

use MLO not mlo to match the names generated by u-boot builds

Make use of u-boot 2015.07's unified wandboard config to provide a
miniroot to cover all current wandboard variations.

Unlike the other imx u-boot configs the wandboard config doesn't search
for ext2 only a fat fs.

Grow the ramdisk size to fit the extra u-boot files.

From Roman Kravchuk.

Rename the imx miniroot to nitrogen as it creates "6x_bootscript".
Add a miniroot for the CuBox-i which needs u-boot at a particular
offset in the sd image to boot. Based on changes made by Patrick
Wildt in bitrig.

Now all the socs use the same va entry point and don't have any
conflicting symbols we can combine the configs.

Multiple umg files are still required however. The bsd.umg target in
the kernel is replaced by targets for bsd.IMX.umg, bsd.OMAP.umg and
bsd.SUNXI.umg.

Rename miniroot-sunxi to miniroot-cubie as the u-boot included
in the image is for Cubieboard1. Discussed with bmercer@
While here switch from using the separate spl and u-boot images
to the combined spl and u-boot 'u-boot-sunxi-with-spl.bin'.

Fix script to allow it to work on both SD and eMMC. -moj ok deraadt@ nick@

hookup sunxi bits for miniroot and ramdisk, tested on pcduino.
note that on boards without ahci you will need to install to usb and still
boot of sd, at least until there's support for the sd slot.

ok patrick@

Revamp ARMv7 ramdisk and miniroot creation process.

Instead of running mkuboot during install, we call it on during
the release build, so that we can also ship bootable images
of the generic and the ramdisk kernel.

We can now build miniroots for imx, too. The installer also
can recognize the SoC and makes decision based on it.

Use ext2fs for i.MX6 based devices.

Tar the bootloader files to save some space.

ok syl@

Update ARMv7's release build process to build kernels and ramdisks
per SoC. It's heavily based on the SGI port.

ok florian@

Beagle has been replaced by armv7.