Change Details

Adds support for FriendlyArm NanoPi R4S (4GB/LPDDR4). This is basically a copy of the ROCKPRO64 config but with the correct u-boot. There is a problem with the MAC address for the second NIC (RealTek, labelled LAN) because it is written (or parts of it) in a EEPROM so the device is currently detected properly but comes up without MAC address. The manufacturer has implemented this in u-boot [1] but Linux distros seem to factorize to fix this in the kernel. Patches to get that EEPROM visible do exist already [2] but I have not seen a final decision yet. For the moment the easiest way was to get the MAC address by booting one of the vendor images and then set it in FreeBSD manually like this: ifconfig re0 link 12:89:1E:60:A1:9C [1] https://github.com/friendlyarm/uboot-rockchip/blob/244492a7a5451eca042d3ec7ccff8de6e23dd288/board/friendlyarm/nanopi4/nanopi4.c#L49 [2] https://lkml.org/lkml/2021/6/10/297

Adds support for FriendlyArm NanoPi R4S (4GB/LPDDR4). This is basically a copy of the ROCKPRO64 config but with the correct u-boot. There is a problem with the MAC address for the second NIC (RealTek, labelled LAN) because it is written (or parts of it) in a EEPROM so the device is currently detected properly but comes up without MAC address. The manufacturer has implemented this in u-boot [1] but Linux distros seem to favorize to fix this in the kernel. Patches to get that EEPROM visible do exist already [2] but I have not seen a final decision yet. For the moment the easiest way was to get the MAC address by booting one of the vendor images and then set it in FreeBSD manually like this: ifconfig re0 link 12:89:1E:60:A1:9C [1] https://github.com/friendlyarm/uboot-rockchip/blob/244492a7a5451eca042d3ec7ccff8de6e23dd288/board/friendlyarm/nanopi4/nanopi4.c#L49 [2] https://lkml.org/lkml/2021/6/10/297

Adds support for FriendlyArm NanoPi R4S (4GB/LPDDR4). This is basically a copy of the ROCKPRO64 config but with the correct u-boot. There is a problem with the MAC address for the second NIC (RealTek, labelled LAN) because it is written (or parts of it) in a EEPROM so the device is currently detected properly but comes up without MAC address. The manufacturer has implemented this in u-boot [1] but Linux distros seem to factfavorize to fix this in the kernel. Patches to get that EEPROM visible do exist already [2] but I have not seen a final decision yet. For the moment the easiest way was to get the MAC address by booting one of the vendor images and then set it in FreeBSD manually like this: ifconfig re0 link 12:89:1E:60:A1:9C [1] https://github.com/friendlyarm/uboot-rockchip/blob/244492a7a5451eca042d3ec7ccff8de6e23dd288/board/friendlyarm/nanopi4/nanopi4.c#L49 [2] https://lkml.org/lkml/2021/6/10/297