NetBSD has fixes to its RPi4 genet support, do they suggest any changes for FreeBSD?

[Mark Millard]

This mattered for my attempted use of https://rpi4-uefi.dev 's v1.13
and NetBSD-current for using the Ethernet via NetBSD on the RPi4.

QUOTE
On 2020-May-27, at 03:24, Jared McNeill <jmcneill at invisible.ca> wrote:

Less than an hour after that build's timestamp I committed some fixes in this area:

 http://mail-index.netbsd.org/source-changes/2020/05/25/msg117718.html
 http://mail-index.netbsd.org/source-changes/2020/05/25/msg117719.html
 http://mail-index.netbsd.org/source-changes/2020/05/25/msg117720.html

Hopefully the next image will work better for you.
END QUOTE

It did work better.

Prior to the update, the RPi4 could see traffic over its
Ethernet but other devices could not see traffic from
the RPi4 (tcpdump results). This prevented the likes of
DHCP client from assigning an IPv4 address in the
intended range (which is how I initially noticed
that there was a problem).

As of installing and trying todays:

https://www.armbsd.org/arm/netbsd-9/202005261610Z/NetBSD-evbarm-aarch64-202005261610Z-generic.img.gz

(that has the above fixes), DHCP client works fine and
an IPv4 address in the intended range is assigned.

I've no clue if any of the NetBSD fixes suggest any FreeBSD
genet changes or not. (FYI: The fixes are in turn based on
OpenBSD code.)

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)