what driver is responsible for mmcblk devices? about nixos-bpir3-example HOT 2 CLOSED

I saw someone else using it so I figured it'd be fine.

I don't see how the example "homelab" configuration could be functional. It is applying all four of the devicetree overlays. The NOR and NAND ones and the SD, and eMMC overlays are mutually exclusive due to the wiring of the BPi-R3.

here's my config

I might have missed it, but I don't see any devicetree overlays being applied in your config; for the storage device to be detected, you'll need to apply the appropriate devicetree overlay for your backing storage at build time.

For SD based boot, the following. Though this repo chooses to use a local copy of said file.

{config, ...}: {
  hardware.deviceTree.overlays = [
      {
        name = "mt7986a-bananapi-bpi-r3-sd.dtbo";
        dtboFile = "${config.boot.kernelPackages.kernel}/dtbs/mediatek/mt7986a-bananapi-bpi-r3-sd.dtbo";
      }
  ];
}

Module wise, it's mtk-sd.

Do I have to compile a custom kernel, or can I use the default one?

I suspect you can get the device to boot without a custom kernel, but I expect none of the ethernet ports will be functional. I had to compile in kernel/drivers/net/ethernet/mediatek/mtk_eth.ko and kernel/net/dsa/tag_mtk.ko.
Someone reported this upstream, but it looks like they didn't follow up on the response; see https://lore.kernel.org/all/[email protected]/

There's similar issues with kernel/drivers/pci/controller/pcie-mediatek-gen3.ko as well IIRC.

from nixos-bpir3-example.

Thanks, I confused dtb and dtbo files so I thought setting deviceTree.filter would be enough.

Ethernet didn't work (I did use a custom kernel in the end, but mtk_eth wasn't compiled in), so I'll rebuild the kernel and try again.

Edit: it worked, had to add the eeprom data overlay for wifi to work as well

from nixos-bpir3-example.