)]}'
{
  "commit": "ea27a6e524690a7a376764fd60a37ec1b78ec8f3",
  "tree": "91463bba7261a69dc84fdf14800c3331046447de",
  "parents": [
    "c0124d13afa0b1399238b1ce94a3f20ea7ffbd91"
  ],
  "author": {
    "name": "Nico Huber",
    "email": "nico.h@gmx.de",
    "time": "Fri Oct 03 14:21:00 2025 +0200"
  },
  "committer": {
    "name": "Nico Huber",
    "email": "nico.h@gmx.de",
    "time": "Fri Jan 16 15:32:05 2026 +0000"
  },
  "message": "dediprog: Set i/o lines with protocol v2+\n\nWhen adding support for the v2 protocol, we left a FIXME open\ninstead of setting the i/o lines as before.  Looking into the\n`dpcmd` source code confirms  that the i/o values are now set\nin the lower bits of `wValue` of the USB request.\n\nTraces of Dediprog\u0027s Windows application with an SF600Plus-G2\nshow that it first sends a request with `wValue \u003d 0x8001` and\n`wIndex \u003d 0x0021` during initialization, then later `wValue \u003d\n0x0L09` by default (L being the LED setting).\n\nIn a ticket[1], test results showed that setting 0x09 fixes\nspurious high-levels on the MISO line with newer SF100 ver-\nsions and certain flash chips.\n\nTests with an SF600Plus-G2 confirmed that the magic 0x9 sets\nCS2 and IO2 high. Adapters map IO2 to IO4 of an SF100 inter-\nface, which again is expected to be high.\n\n[1] https://ticket.coreboot.org/issues/609\n\nChange-Id: Iba5e113adb607a92802cb93a121987920f507fad\nSigned-off-by: Nico Huber \u003cnico.h@gmx.de\u003e\nReviewed-on: https://review.sourcearcade.org/c/flashprog/+/349\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "96fb3d5a91043a1046c0459caa8b84925f74faf1",
      "old_mode": 33188,
      "old_path": "dediprog.c",
      "new_id": "d77cbfb010358ad1249796693f3b3e645fe78aee",
      "new_mode": 33188,
      "new_path": "dediprog.c"
    }
  ]
}