Provide MI PMAP support on AARCH64

Stop building TISDP2420.

Remove commented out kernel configs

By default, do not install any bootable images.

The previous commit introduced the ability to install a set of
bootable images as a normal part of a release build. While this made
it easy to install bootable images, the contents of a release build
depend on whether or not U-Boot packages are installed in /usr/pkgsrc,
which is the default location searched by installboot(8).

This commit requires users to explicitly list the bootable images to
be installed, which by default is none (i.e., prior behavior).

Create bootable images in ${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg.

Release builds for arm platforms create compressed images in
${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg. However, in some
cases, e.g., armv7.img.gz, they are not bootable. Consequently, boot
blocks must be manually installed in the images, which is an extra
barrier for testing systems or adopting NetBSD. This has prompted
creation of external repositories, e.g., armbsd.org, to host a
collection of bootable images. However, this does not ease the burden
on developers compiling their own systems; for them, manual
installation of boot blocks is still required.

For arm platforms, etc/etc.evbarm/Makefile.inc contains the commands
used to create system images. Because installboot(8) can write boot
blocks directly to system images, a loop through possible boards can
create a series of bootable images during the normal build process.

In the case of many arm platforms, installboot(8) uses U-Boot boot
blocks, which are not part of the NetBSD source code. Developers can,
however, install as many U-Boot boot blocks as desired, either in the
default location of /usr/pkg/share/u-boot or in a set of directories
pointed to by the U-Boot search path, the INSTALLBOOT_UBOOT_PATHS
environment variable. For each board with an available boot block, a
board-specific bootable image will be created in
${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg. If a boot block is
not available, which is the typical situation currently, no additional
image will be created.

This facility creates opportunities to build bootable images for any
number of boards within the scope of a standard release build.
However, that is not required and will not occur without the
intervention of installing U-Boot boot blocks prior to the build.

Build OPENBLOCKS_A6 kernel for evbarmv5-e[bl].

It works --- except for:

- mvsata(4) problems (already reported repeatedly)
- NFS root with mvgbe(4) is weird; the system eventually locks up

Yes, we need to fix them...

Build KUROBOX_PRO for evbarmv5eb.

Other marvell-based machines may also work, but not tested yet.

aarch64: Restrict KERNEL_SUFFIXES to img only

Switch arm64.img to big-endian for aarch64eb, as libsa/efiboot support
bi-endian FFS/disklabel now.

Many thanks to mrg@ for working on this!!

branches: 1.122.2;
Build RPI and RPI2 kernels also for earmv6{,hf}eb.

Build arm64.img for aarch64eb with a LE FFS, and include GENERIC64 in
release builds.

Create a separate Arm64 image that uses MBR partitioning. Amlogic SoCs
require the bootloader to be installed on SD cards at LBA1 which makes
them incompatible with GPT images.

Pass TOOL_GPT to mkimage

Fix typo in comment: IMX21_OLINUXINO --> IMX23_OLINUXINO

Remove references to defunct arm and earm arches

Only build GENERIC kernel for armv7 releases.

Separate devicetree .dts -> .dtb building from kernel builds. They are now
part of a separate set, "dtb.tgz", and only built when MKDTB=yes. This
defaults to yes for earmv[67]* and aarch64, and no everywhere else.

Remove commented out IGEPV2 entry

Remove OVERO from build, and commented out N900 kernel config

Remove BEAGLEBOARDXM from the build

Revert previous for now.

Remove IGEPV2 and OVERO kernels from build

Remove BEAGLEBOARD kernel from list of kernels to build

Unhook BEAGLEBONE kernel from the build

branches: 1.107.2;
Include armv4 for "earm", not just "earmv4".

Switch the kernel7.img RaspberryPi kernel in the armv7 image to GENERIC
and thus reducing the number of kernels built in an evbarmv7 release.

Remove SUNXI kernel config.

Remove TEGRA kernel config.

Remove redundant TARGET_ENDIANNESS check

Include bootarm.efi with releases

G/C VEXPRESS_A15

Another kernel bites te dust.

Remove ODROID-C1 as it is now replaced by GENERIC. Thanks jmcneill.

Match the right MACHINE_ARCHes for GENERIC.

Only add GENERIC to earmv6 and earmv7 builds

Add GENERIC to big-endian KERNEL_SETS

Use the GENERIC kernel where possible in armv7.img and remove the old
kernels from the bulid for SUNXI and TEGRA.

While I'm here disable *_INSTALL kernel builds for boards supported by
armv7.img

Sort

Copy bootaa64.efi to releasedir

branches: 1.93.2;
Add initial support for ARMv8 (AARCH64) (by nisimura@ and ryo@)

- sys/arch/evbarm64 is gone and integrated into sys/arch/evbarm. (by skrll@)
- add support fdt. evbarm/conf/GENERIC64 fdt (bcm2837,sunxi,tegra) based generic 64bit kernel config. (by skrll@, jmcneill@)

branches: 1.92.2;
Add missing RPI FDT build goop, from nick.

Unhook BPI, CUBIEBOARD, and CUBIETRUCK kernels from the build (use SUNXI kernel now)

Creating installation/ramdisk here does not work; it happens too late.

Enable memory disk support in the TEGRA kernel and remove TEGRA_INSTALL.

Replace HUMMINGBIRD_A31 with SUNXI kernel on armv7.img and include .dtb
files for SUNXI and TEGRA kernels on the MSDOS partition.

Copy install ramdisk to releasedir. Provide both a raw ffs and
Legacy U-Boot version of it.

Remove SUNXI_INSTALL kernel

Replace HUMMINGBIRD_A31 with the SUNXI kernel.

Don't try and build VEXPRESS_A15_INSTALL

Replace ALLWINNER_A80 (it's never really worked) with VEXPRESS_A15.

Idea from jmcneill@

add support for i.MX6UltraLite, and
ConnectCore for iMX6UL Starter Board.

branches: 1.81.6;
Add CUBOX to v7 and v7hf.

branches: 1.80.2;
Add initial support for Freescale i.MX7 SoC and
Atmark Techno Armadillo-IoT G3 boards.

Contributed by Internet Initiative Japan Inc.

Remove JETSONTK1 and NYAN-BIG kernels, add a new unified kernel named TEGRA.

Build CUBOX-I kernels

Add a new endianes flag to mkimage and pass it on big endian arm builds.
From Rin Okuyama.

define TOOL_MKUBOOTIMAGE for mkimage

More sorting.

alphabetize armv7 kernels

hook JETSONTK1 kernel into build

Rename beagleboard.img to armv7.img. The new image includes the same
kernels as beagleboard.img plus support for Raspberry Pi 2, ODROID-C1,
Cubieboard2, Cubietruck, Hummingbird A31, and Banana Pi.

hook ODROID-C1 into build

Add RPI2 to kernels build for both earmv[67].

Use the earmv6 built kernels to create an image that can be used on both
RPI and RPI2

Add OVERO to v7 and v7hf.

build INTEGRATOR_CP_INSTALL

build ALLWINNER_A80 kernel

add HUMMINGBIRD_A31 kernel

Add CUBIETRUCK

Add BPI to the list of kernels to build.

branches: 1.63.2;
Initial commit of support for Kobo touch. (i.MX507 or i.MX508)
(http://www.kobo.com)

branches: 1.62.2;
Update list of kernels

modified NetWalker kernel config
* add ARM_HAS_VBAR, FPU_VFP etc.

Add BE version of cubieboard. Plus hf too. And hf for BCM5301X.

Add CUBIEBOARD

Instead of trying to pass two kernels to beagleboard.conf, pass one and
derive the path to the second from the first.

Try to pick up the right location for BEAGLEBONE and BEAGLEBOARD kernels.

fix another typo

Fix a typo

Need to separate BE MACHINE_ARCH so that armv7 can be excluded.

Simply and deal with all the various earm MACHINE_ARCH variants

Use TOOL_GZIP in mkimage, and pass the TOOL_GZIP into it.

Add KUROBOX_PRO as an EVBARM_BOARDS member.

fix ALL_KERNELS handling

Add a new installer image for Raspberry PI to evbarm

Includes the following major changes:

1) Add new configmenu item to sysinst to allow creation of users at
post-install time.
2) Add an sshramdisk type to evbarm, which is a ramdisk with sshd
enabled, allowing users to install on a headless PI by sshing to the
device with the account "sysinst" password "netbsd" to begin the
installation. (Note, neither the account, nor the ssh setup are copied to
the finalized installation image)
3) Change mkimage to build a boot-only image, without the root filesystems.

Much of the sshramdisk code could be reused on other ports easily.

Handle ALL_KERNELS selection

Use HOST_SH to run scripts. Makes mkimage work on SunOS.

Move INTEGRATOR_CP from EVBARM_BOARDS to KERNEL_SETS so an
INTEGRATOR_CP_INSTALL kernel isn't required.

Add support for the ARM Integrator/CP from Sergio L�pez.

The code hasn't been tested on real hardware, but INTEGRATOR_CP config
is useful for QEMU which supports it.

Avoid //

fix output filename for __mkimage macro

fix rpi kernel path, defer image building until after release target is done

avoid dup kernel

add beagleboard

pass more tools down.

Follow a different approach to install the kernel and compress the image.

get the kernel from the release directory.

merge back changes I undid

hook image building for rpi.

build the armv5t, armv6 and armv7 kernels for earm but only the v6 and v7
for earmhf.

Add earmhf support

- Add OPENRD.
- Compile BEAGLEBOARD_INSTALL.

branches: 1.31.2;
Add BCM5301X

Add earm/earmeb changes

Add ub to KERNEL_SUFFIXES.

Add RPI to KERNEL_SETS

branches: 1.27.2;
Bump MV2120 SYMTAB_SPACE.
Add kernels variants for root on the primary partitions of "Drive 1".
Add MV2120 to evbarm release.

add the missing backslash.

Add FriendlyARM Mini2440 support.
- new code for Samsung S3C2440 SoC.
- update for other S3C2xx0.
This port was done by Paul Fleischer.

Enable SHEEVAPLUG for build.

branches: 1.23.8; 1.23.18;
add GEMINI to EVBARM_BOARDS list

Build TISDP2420 kernels

branches: 1.21.12; 1.21.18;
Add a comment reminding to update the release notes if the list of
kernels change.

Add CP3100 and CP3100_INSTALL to kernel/build sets.

Add the GUMSTIX kernels now that the distrib setup tries to find
those kernels.

A port of NetBSD to the I-O DATA HDL-G "Giga LANDISK".

Please refer to following URL for this machine.
http://www.iodata.com/products/products.php?cat=HNP&sc=HDL&ts=2&tsc=14&sc=HDL&pId=HDL-G400U

Add NSLU2 to armeb KERNEL_SETS.

add TWINTAIL.
SMDK2410/2800 now have install kernels.
CVS: ----------------------------------------------------------------------
CVS: CVSROOT cvs.NetBSD.org:/cvsroot

Add TS7200

Build a SMDK2410 kernel.

Don't build a big-endian image on platforms which don't run big-endian.

Build a selection of install kernels.

Add ADI_BRH, IXM1200, and SMDK2800 kernel sets.

- add snap_post, which makes "clean depend all release" in ../distrib/
for all platforms.
- remove now unnecessary replicated code in the various snap_md_post targets
- remove snap_md_pre; nothing uses it any more
- use ${NETBSDSRCDIR} and ${KERNSRCDIR} as appropriate

- consistency cleanup
- ensure INSTALLATION_DIRS contains the appropriate extra directories
for a given platform

Make an Npwr kernel set, and build the Npwr install kernel.

Add an installation/instkernel subdirectory to the release.

Add binary/gzimg to INSTALLATION_DIRS.

Add evbarm snapshot/release targets.

Add the IQ80321 kernel.

Add "bin" to the list of valid kernel suffixes.

Add KERNEL_SUFFIXES; it currently includes "srec".

Add release-building glue for NetBSD/evbarm. Currently we build
two kernel sets: one for INTEGRATOR, one for IQ80310.

Stop building TISDP2420.

Remove commented out kernel configs

By default, do not install any bootable images.

The previous commit introduced the ability to install a set of
bootable images as a normal part of a release build. While this made
it easy to install bootable images, the contents of a release build
depend on whether or not U-Boot packages are installed in /usr/pkgsrc,
which is the default location searched by installboot(8).

This commit requires users to explicitly list the bootable images to
be installed, which by default is none (i.e., prior behavior).

Create bootable images in ${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg.

Release builds for arm platforms create compressed images in
${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg. However, in some
cases, e.g., armv7.img.gz, they are not bootable. Consequently, boot
blocks must be manually installed in the images, which is an extra
barrier for testing systems or adopting NetBSD. This has prompted
creation of external repositories, e.g., armbsd.org, to host a
collection of bootable images. However, this does not ease the burden
on developers compiling their own systems; for them, manual
installation of boot blocks is still required.

For arm platforms, etc/etc.evbarm/Makefile.inc contains the commands
used to create system images. Because installboot(8) can write boot
blocks directly to system images, a loop through possible boards can
create a series of bootable images during the normal build process.

In the case of many arm platforms, installboot(8) uses U-Boot boot
blocks, which are not part of the NetBSD source code. Developers can,
however, install as many U-Boot boot blocks as desired, either in the
default location of /usr/pkg/share/u-boot or in a set of directories
pointed to by the U-Boot search path, the INSTALLBOOT_UBOOT_PATHS
environment variable. For each board with an available boot block, a
board-specific bootable image will be created in
${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg. If a boot block is
not available, which is the typical situation currently, no additional
image will be created.

This facility creates opportunities to build bootable images for any
number of boards within the scope of a standard release build.
However, that is not required and will not occur without the
intervention of installing U-Boot boot blocks prior to the build.

Build OPENBLOCKS_A6 kernel for evbarmv5-e[bl].

It works --- except for:

- mvsata(4) problems (already reported repeatedly)
- NFS root with mvgbe(4) is weird; the system eventually locks up

Yes, we need to fix them...

Build KUROBOX_PRO for evbarmv5eb.

Other marvell-based machines may also work, but not tested yet.

aarch64: Restrict KERNEL_SUFFIXES to img only

Switch arm64.img to big-endian for aarch64eb, as libsa/efiboot support
bi-endian FFS/disklabel now.

Many thanks to mrg@ for working on this!!

branches: 1.122.2;
Build RPI and RPI2 kernels also for earmv6{,hf}eb.

Build arm64.img for aarch64eb with a LE FFS, and include GENERIC64 in
release builds.

Create a separate Arm64 image that uses MBR partitioning. Amlogic SoCs
require the bootloader to be installed on SD cards at LBA1 which makes
them incompatible with GPT images.

Pass TOOL_GPT to mkimage

Fix typo in comment: IMX21_OLINUXINO --> IMX23_OLINUXINO

Remove references to defunct arm and earm arches

Only build GENERIC kernel for armv7 releases.

Separate devicetree .dts -> .dtb building from kernel builds. They are now
part of a separate set, "dtb.tgz", and only built when MKDTB=yes. This
defaults to yes for earmv[67]* and aarch64, and no everywhere else.

Remove commented out IGEPV2 entry

Remove OVERO from build, and commented out N900 kernel config

Remove BEAGLEBOARDXM from the build

Revert previous for now.

Remove IGEPV2 and OVERO kernels from build

Remove BEAGLEBOARD kernel from list of kernels to build

Unhook BEAGLEBONE kernel from the build

branches: 1.107.2;
Include armv4 for "earm", not just "earmv4".

Switch the kernel7.img RaspberryPi kernel in the armv7 image to GENERIC
and thus reducing the number of kernels built in an evbarmv7 release.

Remove SUNXI kernel config.

Remove TEGRA kernel config.

Remove redundant TARGET_ENDIANNESS check

Include bootarm.efi with releases

G/C VEXPRESS_A15

Another kernel bites te dust.

Remove ODROID-C1 as it is now replaced by GENERIC. Thanks jmcneill.

Match the right MACHINE_ARCHes for GENERIC.

Only add GENERIC to earmv6 and earmv7 builds

Add GENERIC to big-endian KERNEL_SETS

Use the GENERIC kernel where possible in armv7.img and remove the old
kernels from the bulid for SUNXI and TEGRA.

While I'm here disable *_INSTALL kernel builds for boards supported by
armv7.img

Sort

Copy bootaa64.efi to releasedir

branches: 1.93.2;
Add initial support for ARMv8 (AARCH64) (by nisimura@ and ryo@)

- sys/arch/evbarm64 is gone and integrated into sys/arch/evbarm. (by skrll@)
- add support fdt. evbarm/conf/GENERIC64 fdt (bcm2837,sunxi,tegra) based generic 64bit kernel config. (by skrll@, jmcneill@)

branches: 1.92.2;
Add missing RPI FDT build goop, from nick.

Unhook BPI, CUBIEBOARD, and CUBIETRUCK kernels from the build (use SUNXI kernel now)

Creating installation/ramdisk here does not work; it happens too late.

Enable memory disk support in the TEGRA kernel and remove TEGRA_INSTALL.

Replace HUMMINGBIRD_A31 with SUNXI kernel on armv7.img and include .dtb
files for SUNXI and TEGRA kernels on the MSDOS partition.

Copy install ramdisk to releasedir. Provide both a raw ffs and
Legacy U-Boot version of it.

Remove SUNXI_INSTALL kernel

Replace HUMMINGBIRD_A31 with the SUNXI kernel.

Don't try and build VEXPRESS_A15_INSTALL

Replace ALLWINNER_A80 (it's never really worked) with VEXPRESS_A15.

Idea from jmcneill@

add support for i.MX6UltraLite, and
ConnectCore for iMX6UL Starter Board.

branches: 1.81.6;
Add CUBOX to v7 and v7hf.

branches: 1.80.2;
Add initial support for Freescale i.MX7 SoC and
Atmark Techno Armadillo-IoT G3 boards.

Contributed by Internet Initiative Japan Inc.

Remove JETSONTK1 and NYAN-BIG kernels, add a new unified kernel named TEGRA.

Build CUBOX-I kernels

Add a new endianes flag to mkimage and pass it on big endian arm builds.
From Rin Okuyama.

define TOOL_MKUBOOTIMAGE for mkimage

More sorting.

alphabetize armv7 kernels

hook JETSONTK1 kernel into build

Rename beagleboard.img to armv7.img. The new image includes the same
kernels as beagleboard.img plus support for Raspberry Pi 2, ODROID-C1,
Cubieboard2, Cubietruck, Hummingbird A31, and Banana Pi.

hook ODROID-C1 into build

Add RPI2 to kernels build for both earmv[67].

Use the earmv6 built kernels to create an image that can be used on both
RPI and RPI2

Add OVERO to v7 and v7hf.

build INTEGRATOR_CP_INSTALL

build ALLWINNER_A80 kernel

add HUMMINGBIRD_A31 kernel

Add CUBIETRUCK

Add BPI to the list of kernels to build.

branches: 1.63.2;
Initial commit of support for Kobo touch. (i.MX507 or i.MX508)
(http://www.kobo.com)

branches: 1.62.2;
Update list of kernels

modified NetWalker kernel config
* add ARM_HAS_VBAR, FPU_VFP etc.

Add BE version of cubieboard. Plus hf too. And hf for BCM5301X.

Add CUBIEBOARD

Instead of trying to pass two kernels to beagleboard.conf, pass one and
derive the path to the second from the first.

Try to pick up the right location for BEAGLEBONE and BEAGLEBOARD kernels.

fix another typo

Fix a typo

Need to separate BE MACHINE_ARCH so that armv7 can be excluded.

Simply and deal with all the various earm MACHINE_ARCH variants

Use TOOL_GZIP in mkimage, and pass the TOOL_GZIP into it.

Add KUROBOX_PRO as an EVBARM_BOARDS member.

fix ALL_KERNELS handling

Add a new installer image for Raspberry PI to evbarm

Includes the following major changes:

1) Add new configmenu item to sysinst to allow creation of users at
post-install time.
2) Add an sshramdisk type to evbarm, which is a ramdisk with sshd
enabled, allowing users to install on a headless PI by sshing to the
device with the account "sysinst" password "netbsd" to begin the
installation. (Note, neither the account, nor the ssh setup are copied to
the finalized installation image)
3) Change mkimage to build a boot-only image, without the root filesystems.

Much of the sshramdisk code could be reused on other ports easily.

Handle ALL_KERNELS selection

Use HOST_SH to run scripts. Makes mkimage work on SunOS.

Move INTEGRATOR_CP from EVBARM_BOARDS to KERNEL_SETS so an
INTEGRATOR_CP_INSTALL kernel isn't required.

Add support for the ARM Integrator/CP from Sergio L�pez.

The code hasn't been tested on real hardware, but INTEGRATOR_CP config
is useful for QEMU which supports it.

Avoid //

fix output filename for __mkimage macro

fix rpi kernel path, defer image building until after release target is done

avoid dup kernel

add beagleboard

pass more tools down.

Follow a different approach to install the kernel and compress the image.

get the kernel from the release directory.

merge back changes I undid

hook image building for rpi.

build the armv5t, armv6 and armv7 kernels for earm but only the v6 and v7
for earmhf.

Add earmhf support

- Add OPENRD.
- Compile BEAGLEBOARD_INSTALL.

branches: 1.31.2;
Add BCM5301X

Add earm/earmeb changes

Add ub to KERNEL_SUFFIXES.

Add RPI to KERNEL_SETS

branches: 1.27.2;
Bump MV2120 SYMTAB_SPACE.
Add kernels variants for root on the primary partitions of "Drive 1".
Add MV2120 to evbarm release.

add the missing backslash.

Add FriendlyARM Mini2440 support.
- new code for Samsung S3C2440 SoC.
- update for other S3C2xx0.
This port was done by Paul Fleischer.

Enable SHEEVAPLUG for build.

branches: 1.23.8; 1.23.18;
add GEMINI to EVBARM_BOARDS list

Build TISDP2420 kernels

branches: 1.21.12; 1.21.18;
Add a comment reminding to update the release notes if the list of
kernels change.

Add CP3100 and CP3100_INSTALL to kernel/build sets.

Add the GUMSTIX kernels now that the distrib setup tries to find
those kernels.

A port of NetBSD to the I-O DATA HDL-G "Giga LANDISK".

Please refer to following URL for this machine.
http://www.iodata.com/products/products.php?cat=HNP&sc=HDL&ts=2&tsc=14&sc=HDL&pId=HDL-G400U

Add NSLU2 to armeb KERNEL_SETS.

add TWINTAIL.
SMDK2410/2800 now have install kernels.
CVS: ----------------------------------------------------------------------
CVS: CVSROOT cvs.NetBSD.org:/cvsroot

Add TS7200

Build a SMDK2410 kernel.

Don't build a big-endian image on platforms which don't run big-endian.

Build a selection of install kernels.

Add ADI_BRH, IXM1200, and SMDK2800 kernel sets.

- add snap_post, which makes "clean depend all release" in ../distrib/
for all platforms.
- remove now unnecessary replicated code in the various snap_md_post targets
- remove snap_md_pre; nothing uses it any more
- use ${NETBSDSRCDIR} and ${KERNSRCDIR} as appropriate

- consistency cleanup
- ensure INSTALLATION_DIRS contains the appropriate extra directories
for a given platform

Make an Npwr kernel set, and build the Npwr install kernel.

Add an installation/instkernel subdirectory to the release.

Add binary/gzimg to INSTALLATION_DIRS.

Add evbarm snapshot/release targets.

Add the IQ80321 kernel.

Add "bin" to the list of valid kernel suffixes.

Add KERNEL_SUFFIXES; it currently includes "srec".

Add release-building glue for NetBSD/evbarm. Currently we build
two kernel sets: one for INTEGRATOR, one for IQ80310.

By default, do not install any bootable images.

The previous commit introduced the ability to install a set of
bootable images as a normal part of a release build. While this made
it easy to install bootable images, the contents of a release build
depend on whether or not U-Boot packages are installed in /usr/pkgsrc,
which is the default location searched by installboot(8).

This commit requires users to explicitly list the bootable images to
be installed, which by default is none (i.e., prior behavior).

Create bootable images in ${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg.

Release builds for arm platforms create compressed images in
${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg. However, in some
cases, e.g., armv7.img.gz, they are not bootable. Consequently, boot
blocks must be manually installed in the images, which is an extra
barrier for testing systems or adopting NetBSD. This has prompted
creation of external repositories, e.g., armbsd.org, to host a
collection of bootable images. However, this does not ease the burden
on developers compiling their own systems; for them, manual
installation of boot blocks is still required.

For arm platforms, etc/etc.evbarm/Makefile.inc contains the commands
used to create system images. Because installboot(8) can write boot
blocks directly to system images, a loop through possible boards can
create a series of bootable images during the normal build process.

In the case of many arm platforms, installboot(8) uses U-Boot boot
blocks, which are not part of the NetBSD source code. Developers can,
however, install as many U-Boot boot blocks as desired, either in the
default location of /usr/pkg/share/u-boot or in a set of directories
pointed to by the U-Boot search path, the INSTALLBOOT_UBOOT_PATHS
environment variable. For each board with an available boot block, a
board-specific bootable image will be created in
${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg. If a boot block is
not available, which is the typical situation currently, no additional
image will be created.

This facility creates opportunities to build bootable images for any
number of boards within the scope of a standard release build.
However, that is not required and will not occur without the
intervention of installing U-Boot boot blocks prior to the build.

Build OPENBLOCKS_A6 kernel for evbarmv5-e[bl].

It works --- except for:

- mvsata(4) problems (already reported repeatedly)
- NFS root with mvgbe(4) is weird; the system eventually locks up

Yes, we need to fix them...

Build KUROBOX_PRO for evbarmv5eb.

Other marvell-based machines may also work, but not tested yet.

aarch64: Restrict KERNEL_SUFFIXES to img only

Switch arm64.img to big-endian for aarch64eb, as libsa/efiboot support
bi-endian FFS/disklabel now.

Many thanks to mrg@ for working on this!!

branches: 1.122.2;
Build RPI and RPI2 kernels also for earmv6{,hf}eb.

Build arm64.img for aarch64eb with a LE FFS, and include GENERIC64 in
release builds.

Create a separate Arm64 image that uses MBR partitioning. Amlogic SoCs
require the bootloader to be installed on SD cards at LBA1 which makes
them incompatible with GPT images.

Pass TOOL_GPT to mkimage

Fix typo in comment: IMX21_OLINUXINO --> IMX23_OLINUXINO

Remove references to defunct arm and earm arches

Only build GENERIC kernel for armv7 releases.

Separate devicetree .dts -> .dtb building from kernel builds. They are now
part of a separate set, "dtb.tgz", and only built when MKDTB=yes. This
defaults to yes for earmv[67]* and aarch64, and no everywhere else.

Remove commented out IGEPV2 entry

Remove OVERO from build, and commented out N900 kernel config

Remove BEAGLEBOARDXM from the build

Revert previous for now.

Remove IGEPV2 and OVERO kernels from build

Remove BEAGLEBOARD kernel from list of kernels to build

Unhook BEAGLEBONE kernel from the build

branches: 1.107.2;
Include armv4 for "earm", not just "earmv4".

Switch the kernel7.img RaspberryPi kernel in the armv7 image to GENERIC
and thus reducing the number of kernels built in an evbarmv7 release.

Remove SUNXI kernel config.

Remove TEGRA kernel config.

Remove redundant TARGET_ENDIANNESS check

Include bootarm.efi with releases

G/C VEXPRESS_A15

Another kernel bites te dust.

Remove ODROID-C1 as it is now replaced by GENERIC. Thanks jmcneill.

Match the right MACHINE_ARCHes for GENERIC.

Only add GENERIC to earmv6 and earmv7 builds

Add GENERIC to big-endian KERNEL_SETS

Use the GENERIC kernel where possible in armv7.img and remove the old
kernels from the bulid for SUNXI and TEGRA.

While I'm here disable *_INSTALL kernel builds for boards supported by
armv7.img

Sort

Copy bootaa64.efi to releasedir

branches: 1.93.2;
Add initial support for ARMv8 (AARCH64) (by nisimura@ and ryo@)

- sys/arch/evbarm64 is gone and integrated into sys/arch/evbarm. (by skrll@)
- add support fdt. evbarm/conf/GENERIC64 fdt (bcm2837,sunxi,tegra) based generic 64bit kernel config. (by skrll@, jmcneill@)

branches: 1.92.2;
Add missing RPI FDT build goop, from nick.

Unhook BPI, CUBIEBOARD, and CUBIETRUCK kernels from the build (use SUNXI kernel now)

Creating installation/ramdisk here does not work; it happens too late.

Enable memory disk support in the TEGRA kernel and remove TEGRA_INSTALL.

Replace HUMMINGBIRD_A31 with SUNXI kernel on armv7.img and include .dtb
files for SUNXI and TEGRA kernels on the MSDOS partition.

Copy install ramdisk to releasedir. Provide both a raw ffs and
Legacy U-Boot version of it.

Remove SUNXI_INSTALL kernel

Replace HUMMINGBIRD_A31 with the SUNXI kernel.

Don't try and build VEXPRESS_A15_INSTALL

Replace ALLWINNER_A80 (it's never really worked) with VEXPRESS_A15.

Idea from jmcneill@

add support for i.MX6UltraLite, and
ConnectCore for iMX6UL Starter Board.

branches: 1.81.6;
Add CUBOX to v7 and v7hf.

branches: 1.80.2;
Add initial support for Freescale i.MX7 SoC and
Atmark Techno Armadillo-IoT G3 boards.

Contributed by Internet Initiative Japan Inc.

Remove JETSONTK1 and NYAN-BIG kernels, add a new unified kernel named TEGRA.

Build CUBOX-I kernels

Add a new endianes flag to mkimage and pass it on big endian arm builds.
From Rin Okuyama.

define TOOL_MKUBOOTIMAGE for mkimage

More sorting.

alphabetize armv7 kernels

hook JETSONTK1 kernel into build

Rename beagleboard.img to armv7.img. The new image includes the same
kernels as beagleboard.img plus support for Raspberry Pi 2, ODROID-C1,
Cubieboard2, Cubietruck, Hummingbird A31, and Banana Pi.

hook ODROID-C1 into build

Add RPI2 to kernels build for both earmv[67].

Use the earmv6 built kernels to create an image that can be used on both
RPI and RPI2

Add OVERO to v7 and v7hf.

build INTEGRATOR_CP_INSTALL

build ALLWINNER_A80 kernel

add HUMMINGBIRD_A31 kernel

Add CUBIETRUCK

Add BPI to the list of kernels to build.

branches: 1.63.2;
Initial commit of support for Kobo touch. (i.MX507 or i.MX508)
(http://www.kobo.com)

branches: 1.62.2;
Update list of kernels

modified NetWalker kernel config
* add ARM_HAS_VBAR, FPU_VFP etc.

Add BE version of cubieboard. Plus hf too. And hf for BCM5301X.

Add CUBIEBOARD

Instead of trying to pass two kernels to beagleboard.conf, pass one and
derive the path to the second from the first.

Try to pick up the right location for BEAGLEBONE and BEAGLEBOARD kernels.

fix another typo

Fix a typo

Need to separate BE MACHINE_ARCH so that armv7 can be excluded.

Simply and deal with all the various earm MACHINE_ARCH variants

Use TOOL_GZIP in mkimage, and pass the TOOL_GZIP into it.

Add KUROBOX_PRO as an EVBARM_BOARDS member.

fix ALL_KERNELS handling

Add a new installer image for Raspberry PI to evbarm

Includes the following major changes:

1) Add new configmenu item to sysinst to allow creation of users at
post-install time.
2) Add an sshramdisk type to evbarm, which is a ramdisk with sshd
enabled, allowing users to install on a headless PI by sshing to the
device with the account "sysinst" password "netbsd" to begin the
installation. (Note, neither the account, nor the ssh setup are copied to
the finalized installation image)
3) Change mkimage to build a boot-only image, without the root filesystems.

Much of the sshramdisk code could be reused on other ports easily.

Handle ALL_KERNELS selection

Use HOST_SH to run scripts. Makes mkimage work on SunOS.

Move INTEGRATOR_CP from EVBARM_BOARDS to KERNEL_SETS so an
INTEGRATOR_CP_INSTALL kernel isn't required.

Add support for the ARM Integrator/CP from Sergio L�pez.

The code hasn't been tested on real hardware, but INTEGRATOR_CP config
is useful for QEMU which supports it.

Avoid //

fix output filename for __mkimage macro

fix rpi kernel path, defer image building until after release target is done

avoid dup kernel

add beagleboard

pass more tools down.

Follow a different approach to install the kernel and compress the image.

get the kernel from the release directory.

merge back changes I undid

hook image building for rpi.

build the armv5t, armv6 and armv7 kernels for earm but only the v6 and v7
for earmhf.

Add earmhf support

- Add OPENRD.
- Compile BEAGLEBOARD_INSTALL.

branches: 1.31.2;
Add BCM5301X

Add earm/earmeb changes

Add ub to KERNEL_SUFFIXES.

Add RPI to KERNEL_SETS

branches: 1.27.2;
Bump MV2120 SYMTAB_SPACE.
Add kernels variants for root on the primary partitions of "Drive 1".
Add MV2120 to evbarm release.

add the missing backslash.

Add FriendlyARM Mini2440 support.
- new code for Samsung S3C2440 SoC.
- update for other S3C2xx0.
This port was done by Paul Fleischer.

Enable SHEEVAPLUG for build.

branches: 1.23.8; 1.23.18;
add GEMINI to EVBARM_BOARDS list

Build TISDP2420 kernels

branches: 1.21.12; 1.21.18;
Add a comment reminding to update the release notes if the list of
kernels change.

Add CP3100 and CP3100_INSTALL to kernel/build sets.

Add the GUMSTIX kernels now that the distrib setup tries to find
those kernels.

A port of NetBSD to the I-O DATA HDL-G "Giga LANDISK".

Please refer to following URL for this machine.
http://www.iodata.com/products/products.php?cat=HNP&sc=HDL&ts=2&tsc=14&sc=HDL&pId=HDL-G400U

Add NSLU2 to armeb KERNEL_SETS.

add TWINTAIL.
SMDK2410/2800 now have install kernels.
CVS: ----------------------------------------------------------------------
CVS: CVSROOT cvs.NetBSD.org:/cvsroot

Add TS7200

Build a SMDK2410 kernel.

Don't build a big-endian image on platforms which don't run big-endian.

Build a selection of install kernels.

Add ADI_BRH, IXM1200, and SMDK2800 kernel sets.

- add snap_post, which makes "clean depend all release" in ../distrib/
for all platforms.
- remove now unnecessary replicated code in the various snap_md_post targets
- remove snap_md_pre; nothing uses it any more
- use ${NETBSDSRCDIR} and ${KERNSRCDIR} as appropriate

- consistency cleanup
- ensure INSTALLATION_DIRS contains the appropriate extra directories
for a given platform

Make an Npwr kernel set, and build the Npwr install kernel.

Add an installation/instkernel subdirectory to the release.

Add binary/gzimg to INSTALLATION_DIRS.

Add evbarm snapshot/release targets.

Add the IQ80321 kernel.

Add "bin" to the list of valid kernel suffixes.

Add KERNEL_SUFFIXES; it currently includes "srec".

Add release-building glue for NetBSD/evbarm. Currently we build
two kernel sets: one for INTEGRATOR, one for IQ80310.

Create bootable images in ${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg.

Release builds for arm platforms create compressed images in
${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg. However, in some
cases, e.g., armv7.img.gz, they are not bootable. Consequently, boot
blocks must be manually installed in the images, which is an extra
barrier for testing systems or adopting NetBSD. This has prompted
creation of external repositories, e.g., armbsd.org, to host a
collection of bootable images. However, this does not ease the burden
on developers compiling their own systems; for them, manual
installation of boot blocks is still required.

For arm platforms, etc/etc.evbarm/Makefile.inc contains the commands
used to create system images. Because installboot(8) can write boot
blocks directly to system images, a loop through possible boards can
create a series of bootable images during the normal build process.

In the case of many arm platforms, installboot(8) uses U-Boot boot
blocks, which are not part of the NetBSD source code. Developers can,
however, install as many U-Boot boot blocks as desired, either in the
default location of /usr/pkg/share/u-boot or in a set of directories
pointed to by the U-Boot search path, the INSTALLBOOT_UBOOT_PATHS
environment variable. For each board with an available boot block, a
board-specific bootable image will be created in
${RELEASEDIR}/${RELEASEMACHINEDIR}/binary/gzimg. If a boot block is
not available, which is the typical situation currently, no additional
image will be created.

This facility creates opportunities to build bootable images for any
number of boards within the scope of a standard release build.
However, that is not required and will not occur without the
intervention of installing U-Boot boot blocks prior to the build.

Build OPENBLOCKS_A6 kernel for evbarmv5-e[bl].

It works --- except for:

- mvsata(4) problems (already reported repeatedly)
- NFS root with mvgbe(4) is weird; the system eventually locks up

Yes, we need to fix them...

Build KUROBOX_PRO for evbarmv5eb.

Other marvell-based machines may also work, but not tested yet.

aarch64: Restrict KERNEL_SUFFIXES to img only

Switch arm64.img to big-endian for aarch64eb, as libsa/efiboot support
bi-endian FFS/disklabel now.

Many thanks to mrg@ for working on this!!

branches: 1.122.2;
Build RPI and RPI2 kernels also for earmv6{,hf}eb.

Build arm64.img for aarch64eb with a LE FFS, and include GENERIC64 in
release builds.

Create a separate Arm64 image that uses MBR partitioning. Amlogic SoCs
require the bootloader to be installed on SD cards at LBA1 which makes
them incompatible with GPT images.

Pass TOOL_GPT to mkimage

Fix typo in comment: IMX21_OLINUXINO --> IMX23_OLINUXINO

Remove references to defunct arm and earm arches

Only build GENERIC kernel for armv7 releases.

Separate devicetree .dts -> .dtb building from kernel builds. They are now
part of a separate set, "dtb.tgz", and only built when MKDTB=yes. This
defaults to yes for earmv[67]* and aarch64, and no everywhere else.

Remove commented out IGEPV2 entry

Remove OVERO from build, and commented out N900 kernel config

Remove BEAGLEBOARDXM from the build

Revert previous for now.

Remove IGEPV2 and OVERO kernels from build

Remove BEAGLEBOARD kernel from list of kernels to build

Unhook BEAGLEBONE kernel from the build

branches: 1.107.2;
Include armv4 for "earm", not just "earmv4".

Switch the kernel7.img RaspberryPi kernel in the armv7 image to GENERIC
and thus reducing the number of kernels built in an evbarmv7 release.

Remove SUNXI kernel config.

Remove TEGRA kernel config.

Remove redundant TARGET_ENDIANNESS check

Include bootarm.efi with releases

G/C VEXPRESS_A15

Another kernel bites te dust.

Remove ODROID-C1 as it is now replaced by GENERIC. Thanks jmcneill.

Match the right MACHINE_ARCHes for GENERIC.

Only add GENERIC to earmv6 and earmv7 builds

Add GENERIC to big-endian KERNEL_SETS

Use the GENERIC kernel where possible in armv7.img and remove the old
kernels from the bulid for SUNXI and TEGRA.

While I'm here disable *_INSTALL kernel builds for boards supported by
armv7.img

Sort

Copy bootaa64.efi to releasedir

branches: 1.93.2;
Add initial support for ARMv8 (AARCH64) (by nisimura@ and ryo@)

- sys/arch/evbarm64 is gone and integrated into sys/arch/evbarm. (by skrll@)
- add support fdt. evbarm/conf/GENERIC64 fdt (bcm2837,sunxi,tegra) based generic 64bit kernel config. (by skrll@, jmcneill@)

branches: 1.92.2;
Add missing RPI FDT build goop, from nick.

Unhook BPI, CUBIEBOARD, and CUBIETRUCK kernels from the build (use SUNXI kernel now)

Creating installation/ramdisk here does not work; it happens too late.

Enable memory disk support in the TEGRA kernel and remove TEGRA_INSTALL.

Replace HUMMINGBIRD_A31 with SUNXI kernel on armv7.img and include .dtb
files for SUNXI and TEGRA kernels on the MSDOS partition.

Copy install ramdisk to releasedir. Provide both a raw ffs and
Legacy U-Boot version of it.

Remove SUNXI_INSTALL kernel

Replace HUMMINGBIRD_A31 with the SUNXI kernel.

Don't try and build VEXPRESS_A15_INSTALL

Replace ALLWINNER_A80 (it's never really worked) with VEXPRESS_A15.

Idea from jmcneill@

add support for i.MX6UltraLite, and
ConnectCore for iMX6UL Starter Board.

branches: 1.81.6;
Add CUBOX to v7 and v7hf.

branches: 1.80.2;
Add initial support for Freescale i.MX7 SoC and
Atmark Techno Armadillo-IoT G3 boards.

Contributed by Internet Initiative Japan Inc.

Remove JETSONTK1 and NYAN-BIG kernels, add a new unified kernel named TEGRA.

Build CUBOX-I kernels

Add a new endianes flag to mkimage and pass it on big endian arm builds.
From Rin Okuyama.

define TOOL_MKUBOOTIMAGE for mkimage

More sorting.

alphabetize armv7 kernels

hook JETSONTK1 kernel into build

Rename beagleboard.img to armv7.img. The new image includes the same
kernels as beagleboard.img plus support for Raspberry Pi 2, ODROID-C1,
Cubieboard2, Cubietruck, Hummingbird A31, and Banana Pi.

hook ODROID-C1 into build

Add RPI2 to kernels build for both earmv[67].

Use the earmv6 built kernels to create an image that can be used on both
RPI and RPI2

Add OVERO to v7 and v7hf.

build INTEGRATOR_CP_INSTALL

build ALLWINNER_A80 kernel

add HUMMINGBIRD_A31 kernel

Add CUBIETRUCK

Add BPI to the list of kernels to build.

branches: 1.63.2;
Initial commit of support for Kobo touch. (i.MX507 or i.MX508)
(http://www.kobo.com)

branches: 1.62.2;
Update list of kernels

modified NetWalker kernel config
* add ARM_HAS_VBAR, FPU_VFP etc.

Add BE version of cubieboard. Plus hf too. And hf for BCM5301X.

Add CUBIEBOARD

Instead of trying to pass two kernels to beagleboard.conf, pass one and
derive the path to the second from the first.

Try to pick up the right location for BEAGLEBONE and BEAGLEBOARD kernels.

fix another typo

Fix a typo

Need to separate BE MACHINE_ARCH so that armv7 can be excluded.

Simply and deal with all the various earm MACHINE_ARCH variants

Use TOOL_GZIP in mkimage, and pass the TOOL_GZIP into it.

Add KUROBOX_PRO as an EVBARM_BOARDS member.

fix ALL_KERNELS handling

Add a new installer image for Raspberry PI to evbarm

Includes the following major changes:

1) Add new configmenu item to sysinst to allow creation of users at
post-install time.
2) Add an sshramdisk type to evbarm, which is a ramdisk with sshd
enabled, allowing users to install on a headless PI by sshing to the
device with the account "sysinst" password "netbsd" to begin the
installation. (Note, neither the account, nor the ssh setup are copied to
the finalized installation image)
3) Change mkimage to build a boot-only image, without the root filesystems.

Much of the sshramdisk code could be reused on other ports easily.