flashrom: parameterize and passthru patches

Sadly we need at least two different forks of flashrom, with
different patches (and therefore different capabilities) applied to
each.  This commit parameterizes the flashrom expression and
includes those parameters in the `passthru` so downstream
expressions can check whether various needed features are present.

src/util/flashrom/default.nix

@@ -13,6 +13,9 @@
 # chips and can also write to the embedded controller (EC) flash,
 # which is a separate chip
 , forChromebook ? false
+
+, writeProtectSupport ? true
+, overlappingFmapRegionSupport ? false
 }:
 
 stdenv.mkDerivation {
@@ -36,12 +39,13 @@ stdenv.mkDerivation {
   buildInputs = lib.optional (!stdenv.hostPlatform.isStatic) libftdi1
                 ++ [ libusb1 pciutils ];
 
-  patches =
+  patches = lib.optionals (writeProtectSupport && !forChromebook) [
-    if !forChromebook then [
+    # the forChromebook fork already has (Google's version of) the enableWriteProtect patches
     ./0001-implement-wp-enable-disable-for-gigadevice-flash-chi.patch
-      ./0002-layout.c-allow-nested-regions.patch
+  ] ++ lib.optionals forChromebook [
-    ] else [
     ../../platform/kevin/chromebook-flashrom-kludges.patch
+  ] ++ lib.optionals overlappingFmapRegionSupport [
+    ./0002-layout.c-allow-nested-regions.patch
   ];
 
   makeFlags = if !forChromebook then [
@@ -54,6 +58,10 @@ stdenv.mkDerivation {
     mv $out/sbin/flashrom $out/sbin/flashrom-chromebook
   '';
 
+  passthru = {
+    inherit forChromebook writeProtectSupport overlappingFmapRegionSupport;
+  };
+
   meta = with lib; {
     homepage = "https://www.flashrom.org";
     description = "Utility for reading, writing, erasing and verifying flash ROM chips";