1. 26 May, 2014 2 commits
  2. 25 May, 2014 1 commit
  3. 18 May, 2014 1 commit
  4. 16 May, 2014 4 commits
  5. 14 May, 2014 1 commit
  6. 10 May, 2014 1 commit
    • Stefan Tauner's avatar
      Refine messages related to erase/write recovery · a58f6e9b
      Stefan Tauner authored
      
      We are more verbose inside erase_and_write_flash() although it does not
      matter as much as at the end of the whole process in doit().
      
      New output for the non-fatal (i.e. read-protected + successful recovery read) case:
      
      Reading old flash chip contents... done.
      Erasing and writing flash chip... spi_block_erase_d8 failed during command execution at address 0x8000
      Reading current flash chip contents... done. spi_chip_erase_c7 failed during command execution
      FAILED!
      Uh oh. Erase/write failed. Checking if anything has changed.
      Reading current flash chip contents... done.
      Good, writing to the flash chip apparently didn't do anything.
      Please check the connections (especially those to write protection pins) between
      the programmer and the flash chip. If you think the error is caused by flashrom
      please report this on IRC at chat.freenode.net (channel #flashrom) or
      mail flashrom@flashrom.org, thanks!
      
      Corresponding to flashrom svn r1790.
      Signed-off-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
      Acked-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
      a58f6e9b
  7. 09 May, 2014 1 commit
  8. 07 May, 2014 2 commits
  9. 04 May, 2014 2 commits
  10. 03 May, 2014 2 commits
    • Michael Coppola's avatar
      4e7f36ec
    • Stefan Tauner's avatar
      Add a bunch of new/tested stuff and various small changes 20 · c2eec2c9
      Stefan Tauner authored
      Tested mainboards:
      OK:
       - abit BX6 2.0
         Reported by Stefan Tauner
       - Acer EM61SM/EM61PM (used in Acer Aspire T180)
         Reported by Benjamin Bellec
       - ADLINK Express-HR
         Reported by Obermair Thomas
       - ASUS M3N-H/HDMI
         Reported by Franc Serres
       - Attro G5G100-P
         Reported by Christoph Grenz
       - ASRock 960GM-GS3 FX
         Reported by Fuley Istvan
       - Elitegroup P6BAP-A+ (V2.2)
         Reported by Arnaldo Pirrone
       - Elitegroup GeForce7050M-M (V2.0)
         Reported by Leif Middelschulte
       - Fujitsu D3041-A1 (used in ESPRIMO P2560)
         Reported by Daggi Duck
       - GIGABYTE GA-8S648
         Reported by TeslaBIOS
       - GIGABYTE GA-970A-D3P (rev. 1.0)
         Reported by Jean-Francois Pirus
       - GIGABYTE GA-B85M-D3H
         Reported by Mladen Milinković
       - GIGABYTE GA-X79-UD3
         Reported by Jeff O'Neil
       - GIGABYTE GA-X79-UP4 (rev. 1.0)
         Reported by George Spelvin
       - GIGABYTE GA-Z68MA-D2H-B3 (rev. 1.3)
         Reported by Vangelis Skarmoutsos
       - GIGABYTE GA-Z87-HD3
         Reported by virii5
       - ...
      c2eec2c9
  11. 02 May, 2014 1 commit
  12. 27 Apr, 2014 1 commit
  13. 26 Apr, 2014 11 commits
  14. 19 Mar, 2014 2 commits
  15. 17 Mar, 2014 1 commit
  16. 14 Mar, 2014 1 commit
  17. 05 Mar, 2014 1 commit
  18. 21 Nov, 2013 1 commit
  19. 29 Oct, 2013 1 commit
    • Stefan Tauner's avatar
      Ensure DMI strings used in dmi_compare() are not NULL · d1045d8b
      Stefan Tauner authored
      
      Previously the external DMI decoder did not allow this to happen because
      all possible pointers were initialized at startup by the output of
      'dmidecode -s ...' which has default values for all supported types.
      
      The now active internal DMI decoder does work differently: it scans the
      complete DMI table once and copies the available strings. Therefore, strings
      that are not set by the firmware are left at their default value of NULL.
      
      A segfault would arise if the following conditions are all true:
       - the firmware sets up a DMI/SMBIOS table which has at least a correct
         checksum, and
       - that table does *not* define at least one of the DMI strings we use
         for matching (as defined by dmi_strings[] in dmi.c), and
       - there exists a board enable whose PCI IDs are matched by the board,
         and which has a DMI string set that ends with a $ anchor, and
       - the user calls the internal programmer of flashrom without the
         optional mainboard parameter.
      
      This was first observed by Gelip on an abit BF6 using the coreboot port
      for the abit BE6-II V2.0.
      The segfault was reproduced by Idwer Vollering on an ASUS F2A85-M with
      the default DMI values of CONFIG_MAINBOARD_SMBIOS_MANUFACTURER etc.
      overwritten and a forged board enable matching his board.
      Idwer also verified that this patch fixes the problem, thanks a lot!
      
      Corresponding to flashrom svn r1763.
      Signed-off-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
      Acked-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
      d1045d8b
  20. 26 Oct, 2013 1 commit
  21. 25 Oct, 2013 1 commit
    • Stefan Tauner's avatar
      Refactor Intel Chipset Enables · 92d6a861
      Stefan Tauner authored
      
       - Combine enable_flash_ich_4e() and enable_flash_ich_dc() to
         enable_flash_ich_fwh().
       - Remove unjustified (chipset) name parameters from various
         enable_flash_ich* functions.
       - Make Poulsbo and Tunnel Creek use generic enables by refining existing
         functions to work with them, including everything in ichspi.c.
       - Refactor enable_flash_ich_fwh_decode() to be called unconditionally for
         all chipsets.
       - Add support for Intel Atom Centerton (S12x0).
       - Recombine ICH2/3/4/5 to CHIPSET_ICH2345 because we treat them equally
         anyway.
       - Move spibar handling out of ich_init_spi() into enable_flash_ich_spi()
       - Various small cleanups.
      
      Corresponding to flashrom svn r1761.
      Signed-off-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
      Acked-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
      92d6a861
  22. 21 Oct, 2013 1 commit