earm(v5) on RPI

[John Klos <john%ziaspace.com@localhost>]

Hi, all,

I've been running bulk pkgsrc builds of earm packages using a first 
generation Raspberry Pi in part because we can't run an earmv5 chroot on 
earmv7hf or aarch64, and in part because the original Pi has much more 
memory and is faster than, say, a PogoPlug.

However, the SD card I've been using only to boot the kernel died, so I 
started making a new one. Some observations:

earm from NetBSD-9 is broken:

http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-earm/binary/gzimg/rpi.img.gz

It boots, then gives an endless mess of "<jemalloc>: Unsupported system 
page size" messages.

There are no RPI kernels or images here:

http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-earmv5/

These fail on netbsd-9 sources:

./build.sh -j 8 -D ../dest-evbarm -O ../obj-evbarm -T ../tools -m evbarm -a earmv5 tools
rm -Rf ../dest-evbarm ../obj-evbarm ../tools
./build.sh -j 8 -D ../dest-evbarm -O ../obj-evbarm -T ../tools -m evbarm -a earm tools

#      link  dtc/dtc
cc -O -I/usr/src/tools/dtc/../../sys/external/bsd/libfdt/dist 
-I/usr/src/../tools/include -I/usr/src/../tools/include/nbinclude 
-I/usr/src/../tools/include/compat -I/usr/src/tools/compat 
-DHAVE_NBTOOL_CONFIG_H=1 -D_FILE_OFFSET_BITS=64 
-I/usr/src/tools/dtc/../../external/gpl2/dtc/usr.bin/dtc 
-I/usr/src/external/gpl2/dtc/dist -I/usr/src/sys/external/bsd/libfdt/dist 
-o dtc checks.lo data.lo dtc.lo flattree.lo fstree.lo livetree.lo 
srcpos.lo treesource.lo util.lo dtc-lexer.lo dtc-parser.lo 
-L/usr/src/../obj-evbarm/tools/libfdt -lfdt -L/usr/src/../tools/lib 
-lnbcompat -lrt -lz
ld: dtc-parser.lo:(.bss+0x0): multiple definition of `yylloc'; 
dtc-lexer.lo:(.bss+0x0): first defined here

This fails on current, but this could just be a transient issue:

./build.sh -j 8 -D ../dest-evbarm -O ../obj/evbarm -T ../tools -m evbarm -a earmv6hf kernel=GENERIC

--- pmu_fdt.o ---
/usr/current/src/sys/arch/arm/fdt/pmu_fdt.c: In function 'pmu_fdt_init':
/usr/current/src/sys/arch/arm/fdt/pmu_fdt.c:136:3: error: implicit 
declaration of function 'arm_pmu_init' 
[-Werror=implicit-function-declaration]
  136 |   arm_pmu_init();
      |   ^~~~~~~~~~~~

This succeeds on current, but produces a netbsd.img which doesn't boot 
(stays at rainbow screen):

./build.sh -j 8 -D ../dest-evbarm -O ../obj/evbarm -T ../tools -m evbarm -a earmv6hf kernel=RPI

I'm curious if earm(v5) is expected to boot & run on first generation 
Raspberry Pis / Pi Zeros.

There was a discussion about fixing earm(v5) chroots, so I'm going to 
see if I can run -current and build in a kver chroot.

Thanks,
John