Re: aarch64 support added

[Eddy Petrișor <eddy.petrisor+netbsd.org%gmail.com@localhost>]

2018-04-05 11:45 GMT+03:00 Ryo Shimizu <ryo%nerv.org@localhost>:
>
>>What did you mean by "pmap should be work even if PID_MAX >= 65536"?
>>Does that mean that the PIDs are of type uint16 for aarch64?
>
> Currently, pid_t of netbsd is 16bit, and aarch64 ASID is also 16bit.
> I implement as ASID=ProcessID for simplicity.
> But if pid_t will be 32bit or over in the future (?), It will not work.
>
>
>>About "COMPAT_NETBSD32", is that supported in userland in any way?
>
> Yes. same as running i386 binary on amd64, We may become able to
> run arm32 userland binary on aarch64 OS...
>
>
>>So to build NetBSD for pine64 should this be OK?
>>
>>kernel=GENERIC64
>>machine: -m evbarm
>>arch:  -a aarch64
>>dts: sun50i-a64-pine64-plus.dts
>
> That's ok, I think. Unfortunately I don't have PINE64, and not tested on it.
> but it runs on same Allwinner board NanoPi NEO Plus 2 by jmcneill@
> https://twitter.com/jmcwhatever/status/959795604586102784

I had a small vacation, but now I am back and realized that after the
building was done there were several images generated (kernel and
dtbs) and also some sets.
Now I don't know how to piece them together into a single SD card
image or coherent setup.

eddy@feodora:~/usr/src/pine64/netbsd/src/obj/releasedir/evbarm$ tree
.
├── binary
│   ├── gzimg
│   │   └── arm64.img.gz
│   ├── kernel
│   │   ├── bcm2837-rpi-3-b.dtb.gz
│   │   ├── MD5
│   │   ├── netbsd-GENERIC64.bin.gz
│   │   ├── netbsd-GENERIC64.gz
│   │   ├── netbsd-GENERIC64.img.gz
│   │   ├── netbsd-GENERIC64.ub.gz
│   │   ├── SHA512
│   │   ├── sun50i-a64-bananapi-m64.dtb.gz
│   │   ├── sun50i-a64-nanopi-a64.dtb.gz
│   │   ├── sun50i-a64-olinuxino.dtb.gz
│   │   ├── sun50i-a64-orangepi-win.dtb.gz
│   │   ├── sun50i-a64-pine64.dtb.gz
│   │   ├── sun50i-a64-pine64-plus.dtb.gz
│   │   ├── sun50i-a64-pinebook.dtb.gz
│   │   ├── sun50i-a64-sopine-baseboard.dtb.gz
│   │   ├── sun50i-h5-nanopi-neo2.dtb.gz
│   │   ├── sun50i-h5-nanopi-neo-plus2.dtb.gz
│   │   ├── sun50i-h5-orangepi-pc2.dtb.gz
│   │   ├── sun50i-h5-orangepi-prime.dtb.gz
│   │   ├── sun50i-h5-orangepi-zero-plus2.dtb.gz
│   │   ├── tegra210-p2371-0000.dtb.gz
│   │   ├── tegra210-p2371-2180.dtb.gz
│   │   ├── tegra210-p2571.dtb.gz
│   │   └── tegra210-smaug.dtb.gz
│   └── sets
│       ├── base.tgz
│       ├── comp.tgz
│       ├── etc.tgz
│       ├── games.tgz
│       ├── kern-GENERIC64.tgz
│       ├── man.tgz
│       ├── MD5
│       ├── misc.tgz
│       ├── modules.tgz
│       ├── SHA512
│       ├── tests.tgz
│       └── text.tgz
├── installation
│   ├── instkernel
│   └── ramdisk
│       ├── ramdisk.fs
│       └── ramdisk.ub
├── INSTALL.html
├── INSTALL.more
├── INSTALL.ps
└── INSTALL.txt

7 directories, 43 files


Is the build system supposed to generate an sdcard image that can be
written directly to the card with a dd command?
Is such an image generated for rpi3, but not for pine64?

I saw for kernel and u-boot images there are some customizations done
in sys/arch/evbarm/conf/mk.sunxi, and I know for NSLU2 some
instructions on how to deply are in sys/arch/evbarm/nslu2/README, but
I wasn't able to find deploy instructions like those or tools to
generate the assembled images for rpi or sunxi.

Where could I add/modify the code to generate such images or, at
least, some instructions on how to deploy for the pine64/sunxi?