)]}'
{
  "commit": "226037da3d274fdf65e477e9ef1082356830b2c7",
  "tree": "7933e58fbbe2f5ab332423626c2f4611500f12f4",
  "parents": [
    "90eb2269c22ac7991f9d46afc3a4b86f89bc9e82"
  ],
  "author": {
    "name": "Stefan Tauner",
    "email": "stefan.tauner@alumni.tuwien.ac.at",
    "time": "Sat Mar 16 01:22:12 2013 +0000"
  },
  "committer": {
    "name": "Stefan Tauner",
    "email": "stefan.tauner@alumni.tuwien.ac.at",
    "time": "Sat Mar 16 01:22:12 2013 +0000"
  },
  "message": "Fix evil twins of Macronix MX25L1605, MX25L3205, MX25L6405\n\nSimilarly to the patch in r1647 this one updates the chips identified as above\nwith references to and data about their respective twins. Unlike previously this\none deals with the more evil details.\n\nHelge Wagner from GE discovered some problems with chips sharing IDs\nand proposed a patch to tackle (some of) them, see:\nhttp://patchwork.coreboot.org/patch/3709/\nThat patch was bitrotting in our mailboxes for a long time and it is still not\nready for merge, but we increasingly get reports about problems (e.g.\nhttp://paste.flashrom.org/view.php?id\u003d1525) regarding these chips and\nhence must act to ensure users\u0027 safety.\n\nThis patch splits the chip definitions of evil twins into separate ones which\ncorrectly declare the respective attributes (the main problems are the erase\nblock sizes for the 0x20 opcode and hence my changes combine different\nchips with partly different attributes apart from their names as long as the\nerasers layout it the same). This forces the user to select the (right) chip\ndefinition with the -c/--chip parameter and hence will break a number of\npreviously perfectly working environments.\n\n0x2015 is used by and split to\n - MX25L1605 (64kB sectors in 0x20 erases)\n - MX25L1605A/MX25L1606E (4kB in 0x20 erases and an additional 0x52 opcode with 64kB blocks)\n - MX25L1605D/MX25L1608D (4k sectors in 0x20 erases)\n\n0x2016 is used by and split to\n - MX25L3205/MX25L3205A (64kB 0x20)\n - MX25L3205D/MX25L3208D (4kB 0x20)\n - MX25L3206E (4k 0x20, 64k 0x52)\n\n0x2017 is used by and split to\n - MX25L6405/MX25L6405D (64k 0x20)\n - MX25L6406E/MX25L6436E (4k 0x20)\n - MX25L6445E (4k 0x20, 64k 0x52)\n\nBonus: add some minor details to MX25L1635D, MX25L1635E, MX25L3235D,\nMX25L12805D.\n\nTested with MX25L3206E, MX25L64036E.\n\nCorresponding to flashrom svn r1657.\n\nSigned-off-by: Stefan Tauner \u003cstefan.tauner@alumni.tuwien.ac.at\u003e\nAcked-by: Stefan Tauner \u003cstefan.tauner@alumni.tuwien.ac.at\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9d1b923c3741cc8a8efb5524e37f1ae2e3a2a512",
      "old_mode": 33188,
      "old_path": "flashchips.c",
      "new_id": "16726ad812f9367bde1859955233cc2ac286183c",
      "new_mode": 33188,
      "new_path": "flashchips.c"
    },
    {
      "type": "modify",
      "old_id": "c4c72bafab4e8a362c19a5ab6c2799f435d12c57",
      "old_mode": 33188,
      "old_path": "flashchips.h",
      "new_id": "4eebc955cd38ef37c2d489cf9ae890e4933f6e4f",
      "new_mode": 33188,
      "new_path": "flashchips.h"
    }
  ]
}