)]}'
{
  "log": [
    {
      "commit": "4267292b0f368c1633ff3316a53b5f7fbada95f8",
      "tree": "4830de68a91351ef29445ec2a7f7ad8d7145b0b9",
      "parents": [
        "357d596bd552ad157a906289ab13ea6ba7e66e3d"
      ],
      "author": {
        "name": "Paul Mackerras",
        "email": "paulus@samba.org",
        "time": "Mon Sep 12 17:17:36 2005 +1000"
      },
      "committer": {
        "name": "Paul Mackerras",
        "email": "paulus@samba.org",
        "time": "Mon Sep 12 17:17:36 2005 +1000"
      },
      "message": "ppc64: Set up PCI tree from Open Firmware device tree\n\nThis adds code which gives us the option on ppc64 of instantiating the\nPCI tree (the tree of pci_bus and pci_dev structs) from the Open\nFirmware device tree rather than by probing PCI configuration space.\nThe OF device tree has a node for each PCI device and bridge in the\nsystem, with properties that tell us what addresses the firmware has\nconfigured for them and other details.\n\nThere are a couple of reasons why this is needed.  First, on systems\nwith a hypervisor, there is a PCI-PCI bridge per slot under the PCI\nhost bridges.  These PCI-PCI bridges have special isolation features\nfor virtualization.  We can\u0027t write to their config space, and we are\nnot supposed to be reading their config space either.  The firmware\ntells us about the address ranges that they pass in the OF device\ntree.\n\nSecondly, on powermacs, the interrupt controller is in a PCI device\nthat may be behind a PCI-PCI bridge.  If we happened to take an\ninterrupt just at the point when the device or a bridge on the path to\nit was disabled for probing, we would crash when we try to access the\ninterrupt controller.\n\nI have implemented a platform-specific function which is called for\neach PCI bridge (host or PCI-PCI) to say whether the code should look\nin the device tree or use normal PCI probing for the devices under\nthat bridge.  On pSeries machines we use the device tree if we\u0027re\nrunning under a hypervisor, otherwise we use normal probing.  On\npowermacs we use normal probing for the AGP bridge, since the device\nfor the AGP bridge itself isn\u0027t shown in the device tree (at least on\nmy G5), and the device tree for everything else.\n\nThis has been tested on a dual G5 powermac, a partition on a POWER5\nmachine (running under the hypervisor), and a legacy iSeries\npartition.\n\nSigned-off-by: Paul Mackerras \u003cpaulus@samba.org\u003e\n"
    },
    {
      "commit": "1635317facea3094ddf34082cd86797efb1d9f7e",
      "tree": "67d5a4d4c7af00ac4be4608092fec99a32683715",
      "parents": [
        "b28d2582ce8aafe531d909bb9c4dcf29189e786e"
      ],
      "author": {
        "name": "Paul Mackerras",
        "email": "paulus@samba.org",
        "time": "Tue Sep 06 13:17:54 2005 +1000"
      },
      "committer": {
        "name": "Paul Mackerras",
        "email": "paulus@samba.org",
        "time": "Fri Sep 09 22:11:38 2005 +1000"
      },
      "message": "[PATCH] Separate pci bits out of struct device_node\n\nThis patch pulls the PCI-related junk out of struct device_node and\nputs it in a separate structure, struct pci_dn.  The device_node now\njust has a void * pointer in it, which points to a struct pci_dn for\nnodes that represent PCI devices.  It could potentially be used in\nfuture for device-specific data for other sorts of devices, such as\nvirtual I/O devices.\n\nSigned-off-by: Paul Mackerras \u003cpaulus@samba.org\u003e\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"
    }
  ]
}