Investigate reason for workaround on RPI regarding udev add events not handled correctly

[mattiaswal]

Today this script is required for devices using wifi (specially RPI), to correctly detect kernel created wifi interface, and then delete it.

cat board/aarch64/raspberrypi-rpi64/rootfs/usr/share/product/raspberrypi,4-model-b/etc/product/init.d/S01-trigger-udev.sh
#!/bin/sh
udevadm control --reload-rules
udevadm trigger --subsystem-match=net --action=add

This feels like a bandaid patch, must be investigated.

[mattiaswal]

The reason for this is that probe (detecting the product) and product script (moves udev rules to /etc/udev/rules.d/), runs after udev. A solution for this, is to do probe in two stages. First stage: detect product and move product specific files in romfs, then run udev and the full probe after that.