Re: aarch64: a port, or a MACHINE_ARCH under evbarm?

[Martin Husemann <martin%duskware.de@localhost>]

On Fri, Nov 09, 2018 at 03:43:11PM -0500, Greg Troxel wrote:
> It seems there is an earmv8hf hardware type, and that usually (but not
> reliably always?) these cpus also implement "aarch64" in addition to the
> familiar "aarch32" instrructions.

Right, arm v8 is a cpu generation that comes in lots of variations,
some of them implement the familiar arm and thumb instruction set.

Typically you would run NetBSD/evbarm64 on them though (and some cpus do not
implement 32bit stuff at all).

> So, for running on RPI3, or for pinebook64, or various other things,
> what is the build.sh command, and which port is that.  And if the -a
> value is not aarch64 but it's the aarch64 port, what does that mean?

	build.sh -m evbarm64

should do. It is an alias (see the table in build.sh) and does:

> ./build.sh -m evbarm64 tools
===> build.sh command:    ./build.sh -m evbarm64 tools
===> build.sh started:    Sat Nov 10 17:11:15 CET 2018
===> NetBSD version:      8.99.25
===> MACHINE:             evbarm
===> MACHINE_ARCH:        aarch64
...

If you have the right u-boot and (say) a evbarmv7hf userland, you could run
64bit and 32bit kernels interchangably on the same device.

Martin