1. 09 Jun, 2013 1 commit
  2. 01 Jun, 2013 1 commit
  3. 23 May, 2013 1 commit
  4. 03 May, 2013 1 commit
  5. 01 May, 2013 1 commit
  6. 19 Apr, 2013 2 commits
  7. 13 Apr, 2013 1 commit
  8. 07 Apr, 2013 1 commit
  9. 05 Apr, 2013 1 commit
  10. 01 Apr, 2013 8 commits
  11. 27 Mar, 2013 1 commit
  12. 16 Mar, 2013 1 commit
    • Stefan Tauner's avatar
      Fix evil twins of Macronix MX25L1605, MX25L3205, MX25L6405 · 226037da
      Stefan Tauner authored
      Similarly to the patch in r1647 this one updates the chips identified as above
      with references to and data about their respective twins. Unlike previously this
      one deals with the more evil details.
      
      Helge Wagner from GE discovered some problems with chips sharing IDs
      and proposed a patch to tackle (some of) them, see:
      http://patchwork.coreboot.org/patch/3709/
      That patch was bitrotting in our mailboxes for a long time and it is still not
      ready for merge, but we increasingly get reports about problems (e.g.
      http://paste.flashrom.org/view.php?id=1525
      
      ) regarding these chips and
      hence must act to ensure users' safety.
      
      This patch splits the chip definitions of evil twins into separate ones which
      correctly declare the respective attributes (the main problems are the erase
      block sizes for the 0x20 opcode and hence my changes combine different
      chips with partly different attributes apart from their names as long as the
      erasers layout it the same). This forces the user to select the (right) chip
      definition with the -c/--chip parameter and hence will break a number of
      previously perfectly working environments.
      
      0x2015 is used by and split to
       - MX25L1605 (64kB sectors in 0x20 erases)
       - MX25L1605A/MX25L1606E (4kB in 0x20 erases and an additional 0x52 opcode with 64kB blocks)
       - MX25L1605D/MX25L1608D (4k sectors in 0x20 erases)
      
      0x2016 is used by and split to
       - MX25L3205/MX25L3205A (64kB 0x20)
       - MX25L3205D/MX25L3208D (4kB 0x20)
       - MX25L3206E (4k 0x20, 64k 0x52)
      
      0x2017 is used by and split to
       - MX25L6405/MX25L6405D (64k 0x20)
       - MX25L6406E/MX25L6436E (4k 0x20)
       - MX25L6445E (4k 0x20, 64k 0x52)
      
      Bonus: add some minor details to MX25L1635D, MX25L1635E, MX25L3235D,
      MX25L12805D.
      
      Tested with MX25L3206E, MX25L64036E.
      
      Corresponding to flashrom svn r1657.
      Signed-off-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
      Acked-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
      226037da
  13. 15 Mar, 2013 2 commits
  14. 09 Mar, 2013 1 commit
  15. 04 Mar, 2013 2 commits
  16. 03 Mar, 2013 1 commit
  17. 22 Feb, 2013 1 commit
  18. 20 Feb, 2013 1 commit
  19. 04 Feb, 2013 1 commit
    • Stefan Tauner's avatar
      Fix building for MacOSX · e038e908
      Stefan Tauner authored
      
      - Add a new macro named IS_MACOSX to hwaccess.c and use it to enable iopl().
        This was broken since r1638. This fix does *not* restore the very permissive
        concept where iopl() was activated in an #else branch that was inplace before
        r1638.
      - Make printing the image file's size in flashrom.c platform independent.
      
      Bonus: remove definitions of off64_t and lseek64 which are not necessary
      anymore for about 1000 commits.
      
      Thanks to SJ for reporting the issue and testing the solution.
      
      Corresponding to flashrom svn r1648.
      Signed-off-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
      Acked-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
      e038e908
  20. 02 Feb, 2013 1 commit
  21. 15 Jan, 2013 1 commit
  22. 08 Jan, 2013 1 commit
  23. 05 Jan, 2013 1 commit
  24. 04 Jan, 2013 2 commits
  25. 03 Jan, 2013 1 commit
  26. 01 Jan, 2013 1 commit
  27. 30 Dec, 2012 1 commit
  28. 29 Dec, 2012 2 commits