1. 16 Mar, 2010 6 commits
  2. 15 Mar, 2010 1 commit
  3. 14 Mar, 2010 2 commits
  4. 13 Mar, 2010 3 commits
  5. 12 Mar, 2010 1 commit
  6. 11 Mar, 2010 1 commit
  7. 09 Mar, 2010 2 commits
  8. 08 Mar, 2010 1 commit
    • Carl-Daniel Hailfinger's avatar
      Write granularity is chip specific · e8e369fc
      Carl-Daniel Hailfinger authored
      
      The following write granularities exist according to my datasheet
      survey: - 1 bit. Each bit can be cleared individually. - 1 byte. A byte
      can be written once. Further writes to an already written byte cause
      the contents to be either undefined or to stay unchanged. - 128 bytes.
      If less than 128 bytes are written, the rest will be erased. Each write
      to a 128-byte region will trigger an automatic erase before anything is
      written. Very uncommon behaviour. - 256 bytes. If less than 256 bytes
      are written, the contents of the unwritten bytes are undefined.
      
      Note that chips with default 256-byte writes, which keep the original
      contents for unwritten bytes, have a granularity of 1 byte.
      
      Handle 1-bit, 1-byte and 256-byte write granularity.
      
      Corresponding to flashrom svn r927.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarSean Nelson <audiohacked@gmail.com>
      Acked-by: default avatarDavid Hendricks <dhendrix@google.com>
      e8e369fc
  9. 07 Mar, 2010 5 commits
  10. 05 Mar, 2010 1 commit
  11. 03 Mar, 2010 1 commit
  12. 28 Feb, 2010 1 commit
  13. 27 Feb, 2010 2 commits
  14. 26 Feb, 2010 3 commits
  15. 25 Feb, 2010 1 commit
  16. 24 Feb, 2010 3 commits
  17. 22 Feb, 2010 1 commit
  18. 21 Feb, 2010 1 commit
  19. 19 Feb, 2010 1 commit
  20. 18 Feb, 2010 1 commit
  21. 16 Feb, 2010 1 commit
  22. 14 Feb, 2010 1 commit
    • Carl-Daniel Hailfinger's avatar
      Allow the registration of functions to be called at programmer shutdown · cc389fc6
      Carl-Daniel Hailfinger authored
      
      Some programmers want to run certain functions during programmer
      shutdown, but the function choice depends on the code path taken
      during programmer init. Rather than rebuilding the whole init logic in
      the shutdown function, it is now possible to register functions for
      execution on programmer shutdown. The behaviour is similar to atexit(),
      but the registered functions will be run on programmer shutdown instead
      of on exit and the functions will be called with a void * argument
      that is specified on registration. Registered functions must have
      the prototype void function(void *); and will be executed in reverse
      registration order directly before calling the programmer-specific
      shutdown() function. It is recommended to have shutdown() only disable
      programmer/hardware access and leave all code path sensitive shutdown to
      functions registered with register_shutdown().
      
      The most prominent use case is resetting the EC after flashing on
      laptops.
      
      Note: There are quite a few code paths in flashrom which proceed to
      terminate flashrom without any programmer shutdown. Those code paths
      will not get the benefit of register_shutdown() and they should be
      changed wherever possible.
      
      Corresponding to flashrom svn r904.
      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>
      cc389fc6