1. 02 Jun, 2009 2 commits
  2. 31 May, 2009 1 commit
    • Carl-Daniel Hailfinger's avatar
      Add bus type annotation to struct flashchips · 1dfe0ff1
      Carl-Daniel Hailfinger authored
      
      Right now, the annotation only differentiates between SPI and non-SPI.
      Anyone who knows more about a specific flash chip should feel free to
      update it.
      
      The existing flashbus variable was abused to denote the SPI controller
      type. Use an aptly named variable for that purpose.
      
      Once this patch is merged, the chipset/programmer init functions can set
      supported flash chip types and flashrom can automatically select only
      matching probe/read/erase/write functions. A side benefit of that will
      be the elimination of the Winbond W29EE011 vs. AMIC A49LF040A conflict.
      
      Corresponding to flashrom svn r556.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarUwe Hermann <uwe@hermann-uwe.de>
      1dfe0ff1
  3. 29 May, 2009 1 commit
  4. 27 May, 2009 1 commit
  5. 26 May, 2009 1 commit
  6. 21 May, 2009 3 commits
  7. 20 May, 2009 1 commit
  8. 17 May, 2009 2 commits
  9. 16 May, 2009 1 commit
  10. 13 May, 2009 4 commits
  11. 12 May, 2009 1 commit
  12. 09 May, 2009 1 commit
  13. 08 May, 2009 1 commit
  14. 05 May, 2009 1 commit
  15. 04 May, 2009 1 commit
  16. 29 Apr, 2009 1 commit
  17. 23 Apr, 2009 1 commit
  18. 22 Apr, 2009 1 commit
    • Carl-Daniel Hailfinger's avatar
      All "unknown xy SPI chip" entries claim to have status UNTESTED for probe/read/erase/write · 42882fd9
      Carl-Daniel Hailfinger authored
      
      That is incorrect.
      
      A bit of confusion comes from how the #defines are named. We call them
      TEST_BAD_*, but the message printed by flashrom says: "This flash part
      has status NOT WORKING for operations:"
      
      Something that is unimplemented is definitely not working.
      
      Neither of the chip entries mentioned above has erase or write functions
      implemented, so erase and write are not working. Since their size is
      unknown, we can't read them in. That means read is not working as well.
      Probing is a different matter. If a chip-specific probe function had
      matched, we wouldn't have to handle the chip with the "unknown xy SPI
      chip" fallback. I'm tempted to call that "not working" as well, but I'm
      open to discussion on this point.
      
      Corresponding to flashrom svn r439 and coreboot v2 svn r4177.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarUwe Hermann <uwe@hermann-uwe.de>
      42882fd9
  19. 21 Apr, 2009 2 commits
  20. 20 Apr, 2009 1 commit
  21. 19 Apr, 2009 2 commits
  22. 19 Mar, 2009 1 commit
  23. 25 Feb, 2009 1 commit
  24. 22 Feb, 2009 1 commit
  25. 26 Jan, 2009 3 commits
  26. 25 Jan, 2009 1 commit
  27. 24 Jan, 2009 2 commits
  28. 08 Jan, 2009 1 commit