• Carl-Daniel Hailfinger's avatar
    One of the problems is that --force had multiple meanings · 27023768
    Carl-Daniel Hailfinger authored
    - Force chip read by faking probe success.
    - Force chip access even if the chip is bigger than max decode size for
      the flash bus.
    - Force erase even if erase is known bad.
    - Force write even if write is known bad.
    - Force writing even if cbtable tells us that this is the wrong image
      for this board.
    
    This patch cleans up --force usage:
    - Remove any suggestions to use --force for probe/read from flashrom
      output.
    - Don't talk about "success" or "Found chip" if the chip is forced.
    - Add a new internal programmer parameter boardmismatch=force. This
      overrides any mismatch detection from cbtable/image comparisons.
    - Add a new internal programmer parameter laptop=force_I_want_a_brick.
    - Adjust the documentation for --force.
    - Clean up the man page a bit whereever it talks about --force or
      laptops.
    
    Additional changes in this patch:
    - Add warnings about laptops to the documentation.
    - Abort if a laptop is detected. Can be overridden with the progr...
    27023768
dmi.c 4.25 KB