)]}'
{
  "commit": "8130f2d3ec2f7c32876d470edffbe44394d84d16",
  "tree": "4b6fb8163f074056ff12d1f3d28cd911dad2aaa4",
  "parents": [
    "1455b2baea9f4379086cabf1dcc1388c478c745c"
  ],
  "author": {
    "name": "Carl-Daniel Hailfinger",
    "email": "c-d.hailfinger.devel.2006@gmx.net",
    "time": "Mon May 11 14:40:31 2009 +0000"
  },
  "committer": {
    "name": "Carl-Daniel Hailfinger",
    "email": "c-d.hailfinger.devel.2006@gmx.net",
    "time": "Mon May 11 14:40:31 2009 +0000"
  },
  "message": "Check probing results for flash contents\n\nWhen flashrom JEDEC code sends the ID command to the chip, it expects to\nsee IDs in the default flash location.\n\nHowever, sometimes the chip does not react to the ID command, either\nbecause it doesn\u0027t understand the command or because the command never\nreached it. One way to detect this is to compare ID output with flash\nchip contents for the same location. If they are identical, there is a\nhigh chance you\u0027re not actually seeing ID output. Warn the user in that\ncase.\n\nThis patch helps a lot when a chip is not recognized and we want to\ncheck if the probe responses are real IDs or just random flash chip\ncontents.\n\nThis should probably be added to all probe functions, but probe_jedec\nis called for all sizes and thus flashrom will check this condition at\nleast once per size, making sure we can cross-match the warning.\n\nCorresponding to flashrom svn r494.\n\nSigned-off-by: Carl-Daniel Hailfinger \u003cc-d.hailfinger.devel.2006@gmx.net\u003e\nAcked-by: FENG Yu Ning \u003cfengyuning1984@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ac6095ba563840864b8d982076de5a4a947087bc",
      "old_mode": 33188,
      "old_path": "jedec.c",
      "new_id": "bfbd93e1ddaf6c35da143520ca652078eeca7f5a",
      "new_mode": 33188,
      "new_path": "jedec.c"
    }
  ]
}