)]}'
{
  "commit": "6b8cf7724bd0f8ae1f61937c5f40f4dbbda40960",
  "tree": "61102c2ba75447441d54d0cb035e51416a7dc6ce",
  "parents": [
    "9445de76c124e90176b5116cf82f6cd1413f5230"
  ],
  "author": {
    "name": "Bartlomiej Zolnierkiewicz",
    "email": "bzolnier@gmail.com",
    "time": "Wed May 16 00:51:42 2007 +0200"
  },
  "committer": {
    "name": "Bartlomiej Zolnierkiewicz",
    "email": "bzolnier@gmail.com",
    "time": "Wed May 16 00:51:42 2007 +0200"
  },
  "message": "sis5513: PIO mode setup fixes\n\n* limit max PIO mode to PIO4, this driver doesn\u0027t support PIO5 and attempt\n  to program PIO5 by config_art_rwp_pio() could result in incorrect PIO\n  timings being programmed and possibly the data corruption (for \u003c ATA100\n  family chipsets PIO0 timings were used, for ATA100 and ATA100a - the random\n  content of test1 variable was used, for ATA133 - MWDMA0 timings were used)\n\n* BUG() in sis5513_tune_chipset() if somebody tries to force unsupported PIO5,\n  also cleanup this function a bit while at it\n\n* add comment about PIO0 timings for \u003c ATA100 family chipsets\n\n* remove open-coded best PIO mode selection from config_art_rwp_pio(),\n  it contained numerous bugs:\n\n  - it didn\u0027t check for validity of id-\u003eeide_pio_modes and id-\u003eeide_pio_iordy\n    before using them\n\n  - it tried to found out maximum PIO mode basing on minimum IORDY cycle time\n    (moreover wrong cycle times were used for PIO1/5)\n\n  - it was overriding PIO blacklist and conservative PIO \"downgrade\" done\n    by ide_get_best_pio_mode()\n\n* use sis5513_tune_drive() instead of config_art_rwp_pio()\n  in sis5513_config_xfer_rate() so the correct PIO mode is also set\n  on drive even if the device is not IORDY/DMA capable\n\n* config_art_rwp_pio() was always setting the best possible mode and not\n  the wanted one - fix it and move ide_get_best_pio_mode() call to\n  config_chipset_for_pio()\n\n* don\u0027t use ide_find_best_mode() in config_chipset_for_pio(), it was being\n  overriden by config_art_rwp_pio() for the host timings anyway + we need to\n  set the same PIO mode on the device and the host\n\n* pass correct \"pio\" argument (255 instead of 5) to sis5513_tune_drive() call\n  in sis5513_config_xfer_rate() so the best PIO mode is set on the drive\n  and not PIO4\n\n* rename sis5513_tune_drive() to sis5513_tuneproc()\n  and config_chipset_for_pio() to sis5513_tune_driver()\n\n* bump driver version\n\nSigned-off-by: Bartlomiej Zolnierkiewicz \u003cbzolnier@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2bde1b92784a723f89d2bfafb69d58d3a1d9d6f1",
      "old_mode": 33188,
      "old_path": "drivers/ide/pci/sis5513.c",
      "new_id": "bb6cc4aedd63877c877a5b663e874b4883f0d87b",
      "new_mode": 33188,
      "new_path": "drivers/ide/pci/sis5513.c"
    }
  ]
}