)]}'
{
  "commit": "a96aaa3c716e13c62e1a7d93b5e6580e817cd2f5",
  "tree": "88bde45963ab387837755eec887ccb587e33da65",
  "parents": [
    "1338936efbd5301880063461b74eaf883db6e363"
  ],
  "author": {
    "name": "Nico Huber",
    "email": "nico.h@gmx.de",
    "time": "Tue Mar 05 12:56:13 2024 +0100"
  },
  "committer": {
    "name": "Nico Huber",
    "email": "nico.h@gmx.de",
    "time": "Fri Mar 08 18:09:43 2024 +0000"
  },
  "message": "dediprog: Support long writes of 16MiB and more\n\nOriginally, the core of flashprog never sent more than an erase block\nat once to write. And with the strategy to use the smallest erase-block\nsize by default, we never run into any issue with the dediprog driver.\nNow that we write bigger chunks at once, after all necessary erasure,\nit can be an issue when 16MiB or more are sent.\n\nAs all other driver implementations allow arbitrary length writes,\nhandle this with a simple loop inside the dediprog driver.\n\nTested with (WIP) SF600Plus-G2 and W25Q128FV.\n\nChange-Id: I9db2d84964dbdfe25dfdb93148f4687a34150bc8\nSigned-off-by: Nico Huber \u003cnico.h@gmx.de\u003e\nReviewed-on: https://review.sourcearcade.org/c/flashprog/+/98\nReviewed-by: Arthur Heymans \u003carthur@aheymans.xyz\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "866d628b2d486e6737d60ec5cc3375ffe49959e2",
      "old_mode": 33188,
      "old_path": "dediprog.c",
      "new_id": "64caa8a067fb9b0f9644d313fb58b6741c9e4bf4",
      "new_mode": 33188,
      "new_path": "dediprog.c"
    }
  ]
}