1. 18 May, 2011 1 commit
  2. 04 Dec, 2010 1 commit
  3. 02 Nov, 2010 1 commit
  4. 29 Oct, 2010 1 commit
  5. 19 Oct, 2010 1 commit
    • Carl-Daniel Hailfinger's avatar
      Always read the flash chip before writing · 42d38a9d
      Carl-Daniel Hailfinger authored
      
      This will allow flashrom to skip erase of already-erased blocks and to
      skip write of blocks which already have the wanted contents.
      
      Avoid emergency messages by checking if the chip contents after a failed
      write operation (erase/write) are unchanged.
      
      Keep the emergency messages after a failed pure erase. That part is
      debatable because if someone wants erase, he pretty sure doesn't care
      about the flash contents anymore.
      
      Please note that this introduces additional overhead of a full chip read
      before write. This is frowned upon by people with slow programmers. A
      followup patch will make this configurable.
      
      Corresponding to flashrom svn r1215.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarStefan Reinauer <stepan@coreboot.org>
      42d38a9d
  6. 30 Sep, 2010 1 commit
  7. 27 Jul, 2010 1 commit
    • Carl-Daniel Hailfinger's avatar
      Split off programmer.h from flash.h · 5b997c3e
      Carl-Daniel Hailfinger authored
      
      Programmer specific functions are of absolutely no interest to any file
      except those dealing with programmer specific actions (special SPI
      commands and the generic core).
      
      The new header structure is as follows (and yes, improvements are
      possible):
      flashchips.h  flash chip IDs
      chipdrivers.h  chip-specific read/write/... functions
      flash.h  common header for all stuff that doesn't fit elsewhere
      hwaccess.h hardware access functions
      programmer.h  programmer specific functions
      coreboot_tables.h  header from coreboot, internal programmer only
      spi.h SPI command definitions
      
      Corresponding to flashrom svn r1112.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarUwe Hermann <uwe@hermann-uwe.de>
      5b997c3e
  8. 03 Jul, 2010 1 commit
  9. 31 May, 2010 1 commit
  10. 30 May, 2010 1 commit
  11. 28 Apr, 2010 1 commit
    • 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 programmer
      parameter mentioned above.
      - Add "Portable" to the list of DMI strings indicating laptops.
      - Check if a chip specified with -c is known to flashrom.
      - Programmer parameter reliability and consistency fixes.
      - More paranoid self-checks.
      - Improve documentation.
      
      Corresponding to flashrom svn r996.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarMichael Karcher <flashrom@mkarcher.dialup.fu-berlin.de>
      27023768
  12. 13 Dec, 2009 1 commit
    • Carl-Daniel Hailfinger's avatar
      Internal (onboard) programming was the only feature which could not be disabled · 66ef4e5f
      Carl-Daniel Hailfinger authored
      
      Make various pieces of code conditional on support for internal
      programming. Code shared between PCI device programmers and onboard
      programming is now conditional as well.
      
      It is now possible to build only with dummy support:
      make CONFIG_INTERNAL=no CONFIG_NIC3COM=no CONFIG_SATASII=no
      CONFIG_DRKAISER=no CONFIG_SERPROG=no CONFIG_FT2232SPI=no
      
      This allows building for a specific use case only, and it also
      facilitates porting to a new architecture because it is possible to
      focus on highlevel code only.
      
      Note: Either internal or dummy programmer needs to be compiled in due to
      the current behaviour of always picking a default programmer if -p is
      not specified. Picking an arbitrary external programmer as default  
      wouldn't make sense.
      
      Build and runtime tested in all 1024 possible build combinations. The
      only failures are by design as mentioned above.
      
      Corresponding to flashrom svn r797.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarSean Nelson <audiohacked@gmail.com>
      66ef4e5f
  13. 19 Aug, 2009 1 commit
  14. 05 Jun, 2009 1 commit
  15. 16 May, 2009 1 commit
  16. 23 Apr, 2009 1 commit
  17. 12 Jan, 2009 1 commit
  18. 22 Dec, 2008 1 commit
  19. 18 Oct, 2008 1 commit
  20. 11 Jul, 2008 1 commit
  21. 03 Jul, 2008 2 commits
  22. 18 Jun, 2008 1 commit
    • Peter Stuge's avatar
      Force read unknown flash chips · 7ffbc6f9
      Peter Stuge authored
      
      When flash chip detection fails, it is still useful and possible to read the
      flash chip contents. If no flash chip is found in normal probes and the
      -f -r -c CHIPNAME options are given, a successful probe for the specified
      chip is forced, and then flashrom reads the flash chip using either the read
      function for the specified chip, or if there is none, a simple memcpy().
      
      The patch also moves the global variable int force in flashrom.c into main()
      and passes it as a parameter to layout.c:show_id(), which was the only other
      function that used the variable. This is needed to avoid confusion with the
      new parameter int force which is added to flashrom.c:probe_flash() and used
      to force probe success for the chip named in char *chip_to_probe.
      
      Corresponding to flashrom svn r259 and coreboot v2 svn r3367.
      Signed-off-by: default avatarPeter Stuge <peter@stuge.se>
      Acked-by: default avatarWard Vandewege <ward@gnu.org>
      7ffbc6f9
  23. 04 Mar, 2008 1 commit
  24. 18 Jan, 2008 1 commit
  25. 17 Oct, 2007 1 commit
  26. 10 Oct, 2007 2 commits
  27. 23 Aug, 2007 2 commits
  28. 09 May, 2007 1 commit
  29. 14 Apr, 2007 1 commit
  30. 18 Dec, 2005 2 commits
    • Stefan Reinauer's avatar
      Redo image checking in conversion case · 3a431602
      Stefan Reinauer authored
      Please update to this release if you are using flashrom.
      
      Corresponding to flashrom svn r38 and coreboot v2 svn r2147.
      3a431602
    • Stefan Reinauer's avatar
      Multiple unrelated changes · e3705282
      Stefan Reinauer authored
      * make -v switch print debug messages.
      * do case insensitive comparison of mainboards, as wished on the
        mailinglist
      
      Corresponding to flashrom svn r37 and coreboot v2 svn r2146.
      e3705282
  31. 26 Nov, 2005 1 commit