)]}'
{
  "commit": "619baba195d92ec39379e24c151f4a640898d140",
  "tree": "3acb28ffdd3ebbc8f4b99028b69f51c11ff0f105",
  "parents": [
    "aea34e7ae7a40bc72f9f11b5658160dfb4b90c48"
  ],
  "author": {
    "name": "Anton Vorontsov",
    "email": "avorontsov@mvista.com",
    "time": "Wed Jun 09 16:27:08 2010 -0700"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Wed Jun 09 16:27:08 2010 -0700"
  },
  "message": "gianfar: Revive the driver for eTSEC devices (disable timestamping)\n\nSince commit cc772ab7cdcaa24d1fae332d92a1602788644f7a (\"gianfar: Add\nhardware RX timestamping support\"), the driver no longer works on\nat least MPC8313ERDB and MPC8568EMDS boards (and possibly much more\nboards as well).\n\nThat\u0027s how MPC8313 Reference Manual describes RCTRL_TS_ENABLE bit:\n\n  Timestamp incoming packets as padding bytes. PAL field is set\n  to 8 if the PAL field is programmed to less than 8. Must be set\n  to zero if TMR_CTRL[TE]\u003d0.\n\nI see that the commit above sets this bit, but it doesn\u0027t handle\nTMR_CTRL. Manfred probably had this bit set by the firmware for\nhis boards. But obviously this isn\u0027t true for all boards in the\nwild.\n\nAlso, I recall that Freescale BSPs were explicitly disabling the\ntimestamping because of a performance drop.\n\nFor now, the best way to deal with this is just disable the\ntimestamping, and later we can discuss proper device tree bindings\nand implement enabling this feature via some property.\n\nSigned-off-by: Anton Vorontsov \u003cavorontsov@mvista.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1830f3199cb523080b1a880dd5e834ad9fb8d99a",
      "old_mode": 33188,
      "old_path": "drivers/net/gianfar.c",
      "new_id": "46c69cd0655358a74c726d9b0ae56fd1d2c7d0fd",
      "new_mode": 33188,
      "new_path": "drivers/net/gianfar.c"
    }
  ]
}