1. 12 Jun, 2011 1 commit
  2. 11 Jun, 2011 4 commits
  3. 28 May, 2011 1 commit
  4. 26 May, 2011 1 commit
  5. 19 May, 2011 1 commit
  6. 11 May, 2011 2 commits
  7. 03 May, 2011 1 commit
  8. 29 Apr, 2011 2 commits
  9. 17 Mar, 2011 1 commit
  10. 17 Jan, 2011 1 commit
  11. 24 Nov, 2010 1 commit
  12. 05 Oct, 2010 1 commit
  13. 11 Aug, 2010 1 commit
  14. 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
  15. 22 Jul, 2010 1 commit
  16. 14 Jul, 2010 2 commits
  17. 03 Jul, 2010 1 commit
  18. 28 May, 2010 1 commit
  19. 26 May, 2010 1 commit
    • Carl-Daniel Hailfinger's avatar
      Handle the following architectures in generic flashrom code · cceafa2a
      Carl-Daniel Hailfinger authored
      
      - x86/x86_64 (little endian)
      - PowerPC (big endian)
      - MIPS (big+little endian)
      
      No changes to programmer specific code. This means any drivers with MMIO
      access will _not_ suddenly start working on big endian systems, but with
      this patch everything is in place to fix them.
      
      Compilation should work on all architectures listed above for all
      drivers except nic3com and nicrealtek which require PCI Port IO which is
      x86-only for now.
      
      To compile without nic3com and nicrealtek, run
      make distclean
      make CONFIG_NIC3COM=no CONFIG_NICREALTEK=no
      
      Thanks to Misha Manulis for testing early versions of this patch on
      PowerPC (big endian) with the satasii programmer.
      Thanks to Segher Boessenkool for design review and for helping out with
      compiler tricks and pointing out that we need eieio on PowerPC.
      Thanks to Vladimir Serbinenko for compile testing on MIPS (little
      endian) and PowerPC (big endian) and for runtime testing on MIPS (little
      endian).
      Thanks to David Daney for compile testing on MIPS (big endian).
      Thanks to Uwe Hermann for compile and runtime testing on x86_64.
      
      DO NOT RUN flashrom ON NON-X86 AFTER APPLYING THIS PATCH!
      This patch only provides the infrastructure, but does not convert any
      drivers, so flashrom will compile, but it won't do the right thing on
      non-x86 platforms.
      
      Corresponding to flashrom svn r1013.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarMisha Manulis <misha@manulis.com>
      Acked-by: default avatarVladimir 'phcoder/φ-coder' Serbinenko <phcoder@gmail.com>
      Acked-by: default avatarUwe Hermann <uwe@hermann-uwe.de>
      Acked-by: default avatarSegher Boessenkool <segher@kernel.crashing.org>
      cceafa2a
  20. 21 May, 2010 1 commit
  21. 07 May, 2010 1 commit
  22. 25 Mar, 2010 1 commit
  23. 26 Feb, 2010 1 commit
  24. 11 Feb, 2010 1 commit
    • Carl-Daniel Hailfinger's avatar
      Rewrite substantial parts of the ICH SPI support · f15e1abb
      Carl-Daniel Hailfinger authored
      
      This megapatch rewrites substantial parts of ICH SPI to actually do
      what the SPI layer wants instead of its own weird idea about commands
      (running unrequested commands, running modified commands). Besides that,
      there is a fair share of cleanups as well.
      
      - Add JEDEC_EWSR (Enable Write Status Register) to default commands. -
      Mark a no longer used opcode/preopcode table as unused. - Declare all
      commands as non-atomic/standalone by default. The ICH SPI driver has
      no business executing commands (preopcodes) automatically if they were
      not requested. - Automatically adjust preopcode/opcode pairings (like
      WREN+ERASE) based on what the SPI layer requested. The ICH SPI driver
      has no business executing altered opcode pairs as it sees fit. - Fix
      incomplete initialization in the case of a locked down chipset. Leaving
      the first 4 opcodes with uninitialized pairings had unpredictable
      results. - switch() exists for a reason. Nested if() checking on the
      same variable is an interesting style. - Actually check if the requested
      readcnt/writecnt for a command is supported by the hardware instead
      of delivering corrupt/incomplete commands and data. - If a command
      has unsupported readlen/writelen, complain loudly to the user. - Use
      find_opcode instead of open-coding the same stuff in a dozen variations.
      - Introduce infrastructure for updating the command set of unlocked
      chipsets on the fly.
      
      Corresponding to flashrom svn r894.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarDavid Hendricks <dhendrix@google.com>
      f15e1abb
  25. 07 Jan, 2010 1 commit
    • Carl-Daniel Hailfinger's avatar
      Allow one to disable programmer debug messages at compile time · 5609fa75
      Carl-Daniel Hailfinger authored
      
      Programmer debug messages during programmer init/shutdown are useful
      because they print hardware settings and desired configuration.
      
      They help in getting a quick overview of hardware and software state on
      startup and shutdown.
      
      Programmer debug messages during flash chip access are mostly a
      distraction in logs and should only be enabled if someone is having
      problems which are suspected to stem from a programmer hardware or
      programmer software bug. Disable those messages by default, they can be
      reenabled by #define COMM_DEBUG in the affected programmer file.
      
      An added benefit is a tremendous size reduction in verbose
      probe/read/write/erase logs because only flash chip driver messages
      remain. In some cases, logs will shrink from 65 MB to 10 kB or less.
      
      The right(tm) fix would be two different debug levels (DEBUG and SPEW)
      and the ability to differentiate between programmer debug messages and
      flash chip debug messages. Until the design for the message printing
      infrastructure is finished, this is the best stop-gap measure we can
      get.
      
      Corresponding to flashrom svn r834.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarSean Nelson <audioahcked@gmail.com>
      5609fa75
  26. 25 Nov, 2009 1 commit
  27. 22 Oct, 2009 1 commit
    • Carl-Daniel Hailfinger's avatar
      ichspi: remove obnoxious debug message · 0709a782
      Carl-Daniel Hailfinger authored
      
      Since we don't have any debug level printing infrastructure yet, I
      propose to kill the obnoxious debug message in ichspi.c which was added
      to check for correct PREOP handling.
      
      We know the code works fine (after getting a few reports over 100 MB
      long) and there's no point in keeping it around anymore. If there is any
      desire, we can reinstate it as print_spew or whatever once the debug
      level infrastructure is merged, but at that point we probably just are
      happy that the debug output isn't there anymore.
      
      Corresponding to flashrom svn r753.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarLuc Verhaegen <libv@skynet.be>
      0709a782
  28. 18 Sep, 2009 1 commit
  29. 02 Sep, 2009 1 commit
  30. 09 Aug, 2009 1 commit
  31. 22 Jul, 2009 1 commit
  32. 14 Jul, 2009 1 commit
  33. 10 Jul, 2009 1 commit
    • Carl-Daniel Hailfinger's avatar
      Add SPI multicommand infrastructure · d0478299
      Carl-Daniel Hailfinger authored
      
      Some SPI opcodes need to be sent in direct succession after each other
      without any chip deselect happening in between. A prominent example is
      WREN (Write Enable) directly before PP (Page Program). Intel calls the
      first opcode in such a row "preopcode".
      
      Right now, we ignore the direct succession requirement completely and it
      works pretty well because most onboard SPI masters have a timing or
      heuristics which make the problem disappear.
      The FT2232 SPI flasher is different. Since it is an external flasher,
      timing is very different to what we can expect from onboard flashers and
      this leads to failure at slow speeds.
      
      This patch allows any function to submit multiple SPI commands in a
      stream to any flasher. Support in the individual flashers isn't
      implemented yet, so there is one generic function which passes the each
      command in the stream one-by-one to the command functions of the
      selected SPI flash driver.
      Tested-by: default avatarJakob Bornecrantz <wallbraker@gmail.com>
      
      Corresponding to flashrom svn r645.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarJakob Bornecrantz <wallbraker@gmail.com>
      d0478299
  34. 24 Jun, 2009 1 commit