Just in case, display issue is not specific to NanoPi M1, and also reproducible on OrangePi H3.

if you can't, no worries, I can handle that for the merge.

That would be helpful, thanks in advance.

One more question: is it okay to submit two other very similar boards that I don't have on hands? I talking about NanoPi M1 Plus and Libre Computer ALL-H3-CC H3. Chances of anything going wrong with these two is very low as I understand.

Forgot to mention that I used lib.mkDefault because I intended to submit M1 Plus too:

{
  imports = [
    ../friendlyElec-nanoPiM1
  ];

  device = {
    manufacturer = "FriendlyELEC";
    name = "NanoPi M1 Plus";
    identifier = "friendlyElec-nanoPiM1Plus";
    productPageURL = "https://www.friendlyelec.com/index.php?route=product/product&path=69&product_id=176";
  };

  Tow-Boot = {
    defconfig = "nanopi_m1_plus_defconfig";
  };
}

One more question: is it okay to submit two other very similar boards that I don't have on hands? I talking about NanoPi M1 Plus and Libre Computer ALL-H3-CC H3. Chances of anything going wrong with these two is very low as I understand.

It is required for the builds to have been verified to work, so you can submit it a as a draft PR by clearly stating that they have not been tested and testing that testing by owners of the board is welcome. Even though I agree that they are very likely to work, considering it's Allwinner.

It is required for the builds to have been verified to work, so you can submit it a as a draft PR by clearly stating that they have not been tested and testing that testing by owners of the board is welcome. Even though I agree that they are very likely to work, considering it's Allwinner.

Understood. What to do with lib.mkDefault here then? Will you remove it or keep it?

Force-pushsed:

• The rebase on current development
• Squashing the four fixups