)]}'
{
  "log": [
    {
      "commit": "deb2d2ecd43dfc51efe71eed7128fda514da96c6",
      "tree": "ba05339620bc285265f88d2c7c43df5fc25b732c",
      "parents": [
        "500559a92dd36af7cee95ed2f5b7722fb95a82e7"
      ],
      "author": {
        "name": "Benjamin Herrenschmidt",
        "email": "benh@kernel.crashing.org",
        "time": "Tue Aug 11 15:52:06 2009 +1000"
      },
      "committer": {
        "name": "Jesse Barnes",
        "email": "jbarnes@virtuousgeek.org",
        "time": "Wed Sep 09 13:29:36 2009 -0700"
      },
      "message": "PCI/GPU: implement VGA arbitration on Linux\n\nBackground:\nGraphic devices are accessed through ranges in I/O or memory space. While most\nmodern devices allow relocation of such ranges, some \"Legacy\" VGA devices\nimplemented on PCI will typically have the same \"hard-decoded\" addresses as\nthey did on ISA. For more details see \"PCI Bus Binding to IEEE Std 1275-1994\nStandard for Boot (Initialization Configuration) Firmware Revision 2.1\"\nSection 7, Legacy Devices.\n\nThe Resource Access Control (RAC) module inside the X server currently does\nthe task of arbitration when more than one legacy device co-exists on the same\nmachine. But the problem happens when these devices are trying to be accessed\nby different userspace clients (e.g. two server in parallel). Their address\nassignments conflict. Therefore an arbitration scheme _outside_ of the X\nserver is needed to control the sharing of these resources. This document\nintroduces the operation of the VGA arbiter implemented for Linux kernel.\n\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Tiago Vignatti \u003ctiago.vignatti@nokia.com\u003e\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nSigned-off-by: Jesse Barnes \u003cjbarnes@virtuousgeek.org\u003e\n"
    },
    {
      "commit": "c0e09200dc0813972442e550a5905a132768e56c",
      "tree": "d38e635a30ff8b0a2b98b9d7f97cab1501f8209e",
      "parents": [
        "bce7f793daec3e65ec5c5705d2457b81fe7b5725"
      ],
      "author": {
        "name": "Dave Airlie",
        "email": "airlied@redhat.com",
        "time": "Thu May 29 10:09:59 2008 +1000"
      },
      "committer": {
        "name": "Dave Airlie",
        "email": "airlied@redhat.com",
        "time": "Mon Jul 14 10:45:01 2008 +1000"
      },
      "message": "drm: reorganise drm tree to be more future proof.\n\nWith the coming of kernel based modesetting and the memory manager stuff,\nthe everything in one directory approach was getting very ugly and\nstarting to be unmanageable.\n\nThis restructures the drm along the lines of other kernel components.\n\nIt creates a drivers/gpu/drm directory and moves the hw drivers into\nsubdirectores. It moves the includes into an include/drm, and\nsets up the unifdef for the userspace headers we should be exporting.\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\n"
    }
  ]
}