)]}'
{
  "commit": "9499237a1c42a27fbcc7ed1d59e34df2b574cdfb",
  "tree": "d238fd5a6931af24d2efa6536eb17c09bbf5411b",
  "parents": [
    "732547f96ea2442965a24e0ed529d285321a0fff"
  ],
  "author": {
    "name": "Marcel Holtmann",
    "email": "marcel@holtmann.org",
    "time": "Sun Apr 19 19:30:03 2009 +0200"
  },
  "committer": {
    "name": "Marcel Holtmann",
    "email": "marcel@holtmann.org",
    "time": "Sun Apr 19 19:30:03 2009 +0200"
  },
  "message": "Bluetooth: Add workaround for wrong HCI event in eSCO setup\n\nThe Broadcom chips with 2.1 firmware handle the fallback case to a SCO\nlink wrongly when setting up eSCO connections.\n\n  \u003c HCI Command: Setup Synchronous Connection (0x01|0x0028) plen 17\n      handle 11 voice setting 0x0060\n  \u003e HCI Event: Command Status (0x0f) plen 4\n      Setup Synchronous Connection (0x01|0x0028) status 0x00 ncmd 1\n  \u003e HCI Event: Connect Complete (0x03) plen 11\n      status 0x00 handle 1 bdaddr 00:1E:3A:xx:xx:xx type SCO encrypt 0x01\n\nThe Link Manager negotiates the fallback to SCO, but then sends out\na Connect Complete event. This is wrong and the Link Manager should\nactually send a Synchronous Connection Complete event if the Setup\nSynchronous Connection has been used. Only the remote side is allowed\nto use Connect Complete to indicate the missing support for eSCO in\nthe host stack.\n\nThis patch adds a workaround for this which clearly should not be\nneeded, but reality is that broken Broadcom devices are deployed.\n\nBased on a report by Ville Tervo \u003cville.tervo@nokia.com\u003e\n\nSigned-off-by: Marcel Holtman \u003cmarcel@holtmann.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "963f9662eaa8fa9611f683e63150678cf3ac268a",
      "old_mode": 33188,
      "old_path": "net/bluetooth/hci_event.c",
      "new_id": "15f40ea8d544e3ef68dc4d2be853427a70e2b577",
      "new_mode": 33188,
      "new_path": "net/bluetooth/hci_event.c"
    }
  ]
}