)]}'
{
  "commit": "c176dd0442c40d4e98c86848091f628707f9c50a",
  "tree": "56525b2ccf47bf795f3410694ef1e0b58c0130ef",
  "parents": [
    "2d622b03f8d6dd47889ead0a4f5924c02a421df7"
  ],
  "author": {
    "name": "Jon Hunter",
    "email": "jon-hunter@ti.com",
    "time": "Tue May 01 10:05:08 2012 +0000"
  },
  "committer": {
    "name": "Albert ARIBAUD",
    "email": "albert.u.boot@aribaud.net",
    "time": "Tue May 15 08:31:41 2012 +0200"
  },
  "message": "OMAP4: Set fdt_high for OMAP4 devices to enable booting with Device Tree\n\nFor OMAP4 boards, such as the panda-es, that have 1GB of memory the linux\nkernel fails to locate the device tree blob on boot. The reason being is that\nu-boot is copying the DT blob to the upper part of RAM when booting the kernel\nand the kernel is unable to access the blob. By setting the fdt_high variable\nto either 0xffffffff (to prevent the copy) or 0xac000000 (704MB boundary\nof memory for OMAP4) the kernel is able to locate the DT blob and boot.\n\nBased upon following patch by Dirk Behme set the fdt_high variable to allow\nbooting with device tree on OMAP4 boards.\n\n\"7e9603e i.mx6q: configs: Add fdt_high and initrd_high variables\"\n\nCc: Sricharan R \u003cr.sricharan@ti.com\u003e\nCc: Sandeep Paulraj \u003cs-paulraj@ti.com\u003e\nCc: Tom Rini \u003ctrini@ti.com\u003e\nSigned-off-by: Jon Hunter \u003cjon-hunter@ti.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5507c8f4c64c4c316b97a3d8471a887dfb3d98b0",
      "old_mode": 33188,
      "old_path": "include/configs/omap4_common.h",
      "new_id": "072e17bab8f141270efc2f9c33ff6a948e801d84",
      "new_mode": 33188,
      "new_path": "include/configs/omap4_common.h"
    }
  ]
}