I've tried to build core-image-tiny-initramfs, for raspberypi4-64. This fails due to dependency on busybox-mdev that should be created by the busybox recipe. However in this recipe, in: poky/meta/recipe-core/busybox/busybox/defconfig these lines are commented: # CONFIG_MDEV # CONFIG_FEATURE_MDEV_CONF ... This is why the package busybox-mdev never gets built. In my opinion, these options should be activated by default. I can't think of a reason why they are not, requiring another layer to activated them. Activating them make the core-image-tiny-initramfs compile without error. Iuliu.
The mdev feature is controlled by a config fragment, i.e. meta/recipes-core/busybox/busybox/mdev.cfg In meta/recipes-core/busybox/busybox_1.36.1.bb this is controlled by: ${@["", "file://mdev.cfg"][(d.getVar('VIRTUAL-RUNTIME_dev_manager') == 'busybox-mdev')]} \ so it is only enabled when the init manager is selected. I don't think we should enable this unless something is using it. That is a distro policy decision (which can add the cfg to busybox.
And since you are using a raspberrypi4-64 machine, you may want to ask in a meta-rapsberrypi issue on GitHub https://github.com/agherzan/meta-raspberrypi But first make sure you have your "distro" configured properly, as RP said.