)]}'
{
  "log": [
    {
      "commit": "cc62a7eb6396e8be95b9a30053ed09191818b99b",
      "tree": "0f4bbb0d3c9a99402bf19345e4b4ccf7bd94e216",
      "parents": [
        "4c67045bfc2c14a1d3c6040e80eb4a62946282dd"
      ],
      "author": {
        "name": "Kirill Smelkov",
        "email": "kirr@mns.spb.ru",
        "time": "Sun Jul 03 20:36:57 2011 +0400"
      },
      "committer": {
        "name": "Greg Kroah-Hartman",
        "email": "gregkh@suse.de",
        "time": "Fri Jul 08 14:51:33 2011 -0700"
      },
      "message": "USB: EHCI: Allow users to override 80% max periodic bandwidth\n\nThere are cases, when 80% max isochronous bandwidth is too limiting.\n\nFor example I have two USB video capture cards which stream uncompressed\nvideo, and to stream full NTSC + PAL videos we\u0027d need\n\n    NTSC 640x480 YUV422 @30fps      ~17.6 MB/s\n    PAL  720x576 YUV422 @25fps      ~19.7 MB/s\n\nisoc bandwidth.\n\nNow, due to limited alt settings in capture devices NTSC one ends up\nstreaming with max_pkt_size\u003d2688  and  PAL with max_pkt_size\u003d2892, both\nwith interval\u003d1. In terms of microframe time allocation this gives\n\n    NTSC    ~53us\n    PAL     ~57us\n\nand together\n\n    ~110us  \u003e  100us \u003d\u003d 80% of 125us uframe time.\n\nSo those two devices can\u0027t work together simultaneously because the\u0027d\nover allocate isochronous bandwidth.\n\n80% seemed a bit arbitrary to me, and I\u0027ve tried to raise it to 90% and\nboth devices started to work together, so I though sometimes it would be\na good idea for users to override hardcoded default of max 80% isoc\nbandwidth.\n\nAfter all, isn\u0027t it a user who should decide how to load the bus? If I\ncan live with 10% or even 5% bulk bandwidth that should be ok. I\u0027m a USB\nnewcomer, but that 80% set in stone by USB 2.0 specification seems to be\nchosen pretty arbitrary to me, just to serve as a reasonable default.\n\nNOTE 1\n~~~~~~\n\nfor two streams with max_pkt_size\u003d3072 (worst case) both time\nallocation would be 60us+60us\u003d120us which is 96% periodic bandwidth\nleaving 4% for bulk and control.  Alan Stern suggested that bulk then\nwould be problematic (less than 300*8 bittimes left per microframe), but\nI think that is still enough for control traffic.\n\nNOTE 2\n~~~~~~\n\nSarah Sharp expressed concern that maxing out periodic bandwidth\ncould lead to vendor-specific hardware bugs on host controllers, because\n\n\u003e It\u0027s entirely possible that you\u0027ll run into\n\u003e vendor-specific bugs if you try to pack the schedule with isochronous\n\u003e transfers.  I don\u0027t think any hardware designer would seriously test or\n\u003e validate their hardware with a schedule that is basically a violation of\n\u003e the USB bus spec (more than 80% for periodic transfers).\n\nSo far I\u0027ve only tested this patch on my HP Mini 5103 with N10 chipset\n\n    kirr@mini:~$ lspci\n    00:00.0 Host bridge: Intel Corporation N10 Family DMI Bridge\n    00:02.0 VGA compatible controller: Intel Corporation N10 Family Integrated Graphics Controller\n    00:02.1 Display controller: Intel Corporation N10 Family Integrated Graphics Controller\n    00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)\n    00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02)\n    00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 02)\n    00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02)\n    00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02)\n    00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02)\n    00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02)\n    00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02)\n    00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)\n    00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)\n    00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA AHCI Controller (rev 02)\n    01:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)\n    02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8059 PCI-E Gigabit Ethernet Controller (rev 11)\n\nand the system works stable with 110us/uframe (~88%) isoc bandwith allocated for\nabove-mentioned isochronous transfers.\n\nNOTE 3\n~~~~~~\n\nThis feature is off by default. I mean max periodic bandwidth is set to\n100us/uframe by default exactly as it was before the patch. So only those of us\nwho need the extreme settings are taking the risk - normal users who do not\nalter uframe_periodic_max sysfs attribute should not see any change at all.\n\nNOTE 4\n~~~~~~\n\nI\u0027ve tried to update documentation in Documentation/ABI/ thoroughly, but\nonly \"TBD\" was put into Documentation/usb/ehci.txt -- the text there seems\nto be outdated and much needing refreshing, before it could be amended.\n\nCc: Sarah Sharp \u003csarah.a.sharp@linux.intel.com\u003e\nSigned-off-by: Kirill Smelkov \u003ckirr@mns.spb.ru\u003e\nAcked-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n"
    },
    {
      "commit": "254217d1a86f80981e6dfc54d7412931c6f6e80b",
      "tree": "0e4a983df73294aabcfaee56f125fe5b74c5131c",
      "parents": [
        "be8a058b50a90282d32aa638720195e1c327c569"
      ],
      "author": {
        "name": "Andrea Gelmini",
        "email": "andrea.gelmini@gelma.net",
        "time": "Sun May 23 21:56:41 2010 +0200"
      },
      "committer": {
        "name": "Greg Kroah-Hartman",
        "email": "gregkh@suse.de",
        "time": "Tue Aug 10 14:35:34 2010 -0700"
      },
      "message": "USB: Documentation/usb/ehci.txt: Checkpatch cleanup\n\nDocumentation/usb/ehci.txt:12: ERROR: trailing whitespace\n\nSigned-off-by: Andrea Gelmini \u003candrea.gelmini@gelma.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n"
    },
    {
      "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
      "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d",
      "parents": [],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Sat Apr 16 15:20:36 2005 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Sat Apr 16 15:20:36 2005 -0700"
      },
      "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n"
    }
  ]
}