1. 21 May, 2010 1 commit
  2. 19 May, 2010 1 commit
  3. 15 May, 2010 1 commit
  4. 25 Apr, 2010 1 commit
    • Rudolf Marek's avatar
      Fix the DOS port · 837d8107
      Rudolf Marek authored
      
      Now the DS selector limit is set to 4GB and all mmio accesses goes
      through DS, the 1:1 mapping is fixed so the _DS base is taken onto
      account. Plus is that the hwaccess.c needs no change and memcpy etc can
      be used on mmaped space.
      
      Corresponding to flashrom svn r995.
      
      Signed-off-by: Rudolf Marek <r.marek@assembler.cz> 
      Acked-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      837d8107
  5. 27 Mar, 2010 1 commit
    • Carl-Daniel Hailfinger's avatar
      Add runtime and build environment info to the flashrom version message · 132e2ec6
      Carl-Daniel Hailfinger authored
      
      This patch uses code from Idwer Vollering and Maciej Pijanka.
      I've added Makefile support and compiler version printing and
      restructured the code heavily.
      The code prints runtime system information and buildtime libpci
      information (I couldn't find any runtime libpci version function). Due
      to our ability to cross-compile flashrom, buildtime system information
      from "uname -mrs" doesn't help diagnosing any problems. That's why only
      libpci and gcc are buildtime info, and the rest is runtime info.
      
      Examples:
      
      openSUSE 10.3, i686, gcc 4.2.1, with PCI support:
      flashrom v0.9.1-r971 on Linux 2.6.22.19-0.2-default (i686), built with
      libpci 2.2.6, GCC 4.2.1 (SUSE Linux)
      
      openSUSE 10.3, i686, llvm-clang-2.6.99svn97231, with PCI support:
      flashrom v0.9.1-r971 on Linux 2.6.22.19-0.2-default (i686), built with
      libpci 2.2.6, LLVM 1/clang 1
      
      openSUSE 11.1, x86_64, gcc 4.3.2, with PCI support:
      flashrom v0.9.1-r972 on Linux 2.6.27.29-0.1-default (x86_64), built with
      libpci 3.0.1, GCC 4.3.2 [gcc-4_3-branch revision 141291]
      
      openSUSE 10.3, i686, gcc 4.2.1, without PCI support:
      flashrom v0.9.1-r971 on Linux 2.6.22.19-0.2-default (i686), built with
      GCC 4.2.1 (SUSE Linux)
      
      Windows/cygwin, i686, gcc 4.3.4, without PCI support:
      flashrom v0.9.1-r973 on CYGWIN_NT-5.1 1.7.1(0.218/5/3) (i686), built
      with GCC 4.3.4 20090804 (release) 1
      
      FreeBSD 8.0, i386, gcc 4.2.1, with PCI support:
      flashrom v0.9.1-r973 on FreeBSD 8.0-RELEASE-p2 (i386), built with libpci
      3.1.7, GCC 4.2.1 20070719  [FreeBSD]
      
      Corresponding to flashrom svn r987.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Signed-off-by: default avatarIdwer Vollering <vidwer@gmail.com>
      Acked-by: default avatarMaciej Pijanka <maciej.pijanka@gmail.com>
      132e2ec6
  6. 22 Mar, 2010 1 commit
  7. 21 Mar, 2010 1 commit
  8. 19 Mar, 2010 1 commit
  9. 26 Feb, 2010 1 commit
  10. 21 Feb, 2010 1 commit
  11. 19 Feb, 2010 1 commit
  12. 14 Feb, 2010 1 commit
  13. 12 Feb, 2010 1 commit
  14. 28 Jan, 2010 1 commit
    • Sean Nelson's avatar
      Complete the addition of Feature Bits for all Jedec based chips · 35727f76
      Sean Nelson authored
      
      Add FEATURE_SHORT_RESET, FEATURE_LONG_RESET, and FEATURE_EITHER_RESET
      rewrite jedec functions to use getaddrmask
      
      convert write_49f002 to write_jedec_1
      convert write_w39v040c to write_jedec_1
      convert probe_w39v040c to probe_jedec
      convert write_49lf040 to write_jedec_1
      convert write_pm29f002 to write_jedec
      convert write_29f040b to write_jedec_1
      convert probe_29f040b to probe_jedec
      convert erase_chip_29f040b to erase_chip_block_jedec
      convert erase_sector_29f040b to erase_sector_jedec
      convert write_m29f002b to write_jedec
      convert write_m29f002t to write_jedec
      convert *_29f002 to *_jedec
      
      decouple unused files from Makefile:
      am29f040b.c
      en29f002a.c
      m29f002.c
      mx29f002.c
      pm29f002.c
      sst49lf040.c
      w39v040c.c
      w49f002u.c
      
      Corresponding to flashrom svn r886.
      Signed-off-by: default avatarSean Nelson <audiohacked@gmail.com>
      Acked-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarAnders Juel Jensen <andersjjensen@gmail.com>
      35727f76
  15. 22 Jan, 2010 1 commit
  16. 21 Jan, 2010 1 commit
  17. 20 Jan, 2010 1 commit
    • Michael Karcher's avatar
      Matching board via DMI · 6701ee83
      Michael Karcher authored
      
      If a board is not uniquely identifiable by PCI device/subsystem IDs, a
      string can be specified to be looked for (case-sensitive, substring or
      anchored) for now in one of the following DMI items in addition to matching
      the PCI IDs:
       - System Manufacturer
       - System Product Name
       - System Version
       - Baseboard Manufacturer
       - Baseboard Product Name
       - Baseboard Version
      
      Strings are anchored re-like (^ at the beginning, $ at the end), but
      there are no plans to support full regular expressions and matched to any
      of the mentioned fields.
      
      The match is only made if DMI info is available and the string matches.
      If no DMI info is available and the PCI IDs match, a warning is printed
      as the board can not be autodetected.
      
      It's still open to discussion whether we add an DMI override switch to
      specify a string that will definitely match, and whether this switch is
      only used if no DMI is available or whether it overrides or augments DMI
      data.
      
      DMI data is currently read using dmidecode. This tool is available for
      all major platforms except MacOS X. I heard that there also is a MacOS X
      version of dmidecode, but didn't investigate that.
      
      Corresponding to flashrom svn r874.
      Signed-off-by: default avatarMichael Karcher <flashrom@mkarcher.dialup.fu-berlin.de>
      Acked-by: default avatarLuc Verhaegen <libv@skynet.be>
      Acked-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      6701ee83
  18. 19 Jan, 2010 1 commit
    • Carl-Daniel Hailfinger's avatar
      Dediprog SF100 support · d38fac8c
      Carl-Daniel Hailfinger authored
      
      Reverse engineered from USB logs. I never touched that programmer nor
      did I ever see the associated software.
      Disabled by default until it is complete. The driver needs to be hooked
      up to the SPI core before it will do anything besides init and
      diagnostics.
      
      I successfully reverse engineered all commands, but some are still
      somewhat magic.
      Logs from "flashrom -p dediprog -V" are appreciated.
      
      Probe and read should work, erase/write is expected to explode.
      The programmer will set voltage to 0 on exit.
      
      Thanks a lot to Stefan Reinauer and Patrick Georgi for providing USB
      logs and for testing the result.
      
      Corresponding to flashrom svn r870.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarStefan Reinauer <stepan@coresystems.de>
      d38fac8c
  19. 12 Jan, 2010 1 commit
  20. 09 Jan, 2010 1 commit
  21. 08 Jan, 2010 1 commit
  22. 07 Jan, 2010 2 commits
  23. 06 Jan, 2010 1 commit
  24. 24 Dec, 2009 3 commits
  25. 13 Dec, 2009 1 commit
    • Carl-Daniel Hailfinger's avatar
      Internal (onboard) programming was the only feature which could not be disabled · 66ef4e5f
      Carl-Daniel Hailfinger authored
      
      Make various pieces of code conditional on support for internal
      programming. Code shared between PCI device programmers and onboard
      programming is now conditional as well.
      
      It is now possible to build only with dummy support:
      make CONFIG_INTERNAL=no CONFIG_NIC3COM=no CONFIG_SATASII=no
      CONFIG_DRKAISER=no CONFIG_SERPROG=no CONFIG_FT2232SPI=no
      
      This allows building for a specific use case only, and it also
      facilitates porting to a new architecture because it is possible to
      focus on highlevel code only.
      
      Note: Either internal or dummy programmer needs to be compiled in due to
      the current behaviour of always picking a default programmer if -p is
      not specified. Picking an arbitrary external programmer as default  
      wouldn't make sense.
      
      Build and runtime tested in all 1024 possible build combinations. The
      only failures are by design as mentioned above.
      
      Corresponding to flashrom svn r797.
      Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      Acked-by: default avatarSean Nelson <audiohacked@gmail.com>
      66ef4e5f
  26. 24 Nov, 2009 2 commits
  27. 23 Nov, 2009 1 commit
  28. 16 Nov, 2009 2 commits
  29. 03 Oct, 2009 1 commit
  30. 01 Oct, 2009 1 commit
  31. 30 Sep, 2009 1 commit
    • Uwe Hermann's avatar
      Add initial support for flashing some NVIDIA graphics cards · 2bc98f6c
      Uwe Hermann authored
      
      The new option is '-p gfxnvidia', rest of the interface is as usual.
      
      I tested a successful identify and read on a "RIVA TNT2 Model 64/Model 64 Pro"
      card for now, erase and write did NOT work properly so far!
      
      Please do not attempt to write/erase cards yet, unless you can recover!
      
      In addition to the NVIDIA handling code it was required to call
      programmer_shutdown() in a lot more places, otherwise the graphics card
      will be disabled in the init function, but never enabled again as the
      shutdown function is not called.
      The shutdown handling may be changed to use atexit() later.
      
      Corresponding to flashrom svn r737.
      Signed-off-by: default avatarUwe Hermann <uwe@hermann-uwe.de>
      Acked-by: default avatarLuc Verhaegen <libv@skynet.be>
      2bc98f6c
  32. 28 Sep, 2009 1 commit
  33. 16 Sep, 2009 2 commits
  34. 05 Sep, 2009 1 commit