)]}'
{
  "commit": "198fc108ee4c2cd3f08954eae6a819c81c03214b",
  "tree": "153fdb793142ef5ee8e0ab6198dcde32866b062c",
  "parents": [
    "3f16ff608a75c8bf28c8cafed12e076d67a3602a"
  ],
  "author": {
    "name": "Eric Miao",
    "email": "ycmiao@ycmiao-hp520.(none)",
    "time": "Tue Dec 23 17:49:43 2008 +0800"
  },
  "committer": {
    "name": "Eric Miao",
    "email": "eric.miao@marvell.com",
    "time": "Mon Dec 29 18:00:04 2008 +0800"
  },
  "message": "[ARM] pxafb: add support for overlay1 and overlay2 as framebuffer devices\n\nPXA27x and later processors support overlay1 and overlay2 on-top of the\nbase framebuffer (although under-neath the base is also possible). They\nsupport palette and no-palette RGB formats, as well as YUV formats (only\navailable on overlay2). These overlays have dedicated DMA channels and\nbehave in a similar way as a framebuffer.\n\nThis heavily simplified and re-structured work is based on the original\npxafb_overlay.c (which is pending for mainline merge for a long time).\n\nThe major problems with this pxafb_overlay.c are (if you are interested\nin the history):\n\n  1. heavily redundant (the control logics for overlay1 and overlay2 are\n     actually identical except for some small operations,  which are now\n     abstracted into a \u0027pxafb_layer_ops\u0027 structure)\n\n  2. a lot of useless and un-tested code (two workarounds which are now\n     fixed on mature silicons)\n\n  3. cursorfb is actually useless, hardware cursor should not be used\n     this way, and the code was actually un-tested for a long time.\n\nThe code in this patch should be self-explanatory, I tried to add minimum\ncomments. As said, this is basically simplified, there are several things\nstill on the pending list:\n\n  1. palette mode is un-supported and un-tested (although re-using the\n     palette code of the base framebuffer is actually very easy now with\n     previous clean-up patches)\n\n  2. fb_pan_display for overlay(s) is un-supported\n\n  3. the base framebuffer can actually be abstracted by \u0027pxafb_layer\u0027 as\n     well, which will help further re-use of the code and keep a better\n     and consistent structure. (This is the reason I named it \u0027pxafb_layer\u0027\n     instead of \u0027pxafb_overlay\u0027 or something alike)\n\nSee Documentation/fb/pxafb.txt for additional usage information.\n\nSigned-off-by: Eric Miao \u003ceric.miao@marvell.com\u003e\nCc: Rodolfo Giometti \u003cgiometti@linux.it\u003e\nSigned-off-by: Eric Miao \u003cycmiao@ycmiao-hp520.(none)\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ad94b5ca009518aa9f277c8f837ae4e4c3ac4207",
      "old_mode": 33188,
      "old_path": "Documentation/fb/pxafb.txt",
      "new_id": "d143a0a749f9ff3d975e7d0f62b89bb05c0e0620",
      "new_mode": 33188,
      "new_path": "Documentation/fb/pxafb.txt"
    },
    {
      "type": "modify",
      "old_id": "aff3b876a7bfc8aefdf6e676115e39782282c676",
      "old_mode": 33188,
      "old_path": "arch/arm/mach-pxa/include/mach/regs-lcd.h",
      "new_id": "f82dcea792d9523f7b25b149a900f6567de43cd5",
      "new_mode": 33188,
      "new_path": "arch/arm/mach-pxa/include/mach/regs-lcd.h"
    },
    {
      "type": "modify",
      "old_id": "3f3ce13fef431450909e12cb91646534c68cf46f",
      "old_mode": 33188,
      "old_path": "drivers/video/Kconfig",
      "new_id": "486d81ca02a30367b68cc04476aa3b4fce7fea21",
      "new_mode": 33188,
      "new_path": "drivers/video/Kconfig"
    },
    {
      "type": "modify",
      "old_id": "7935706a75652e67f8338d938300b4686e3ef508",
      "old_mode": 33188,
      "old_path": "drivers/video/pxafb.c",
      "new_id": "3a41ea10e8ec9c9fd84cc57ba648f85cb0dcd146",
      "new_mode": 33188,
      "new_path": "drivers/video/pxafb.c"
    },
    {
      "type": "modify",
      "old_id": "ae3cbc1ca64fa46a32d57f82b0e28c70696b8c50",
      "old_mode": 33188,
      "old_path": "drivers/video/pxafb.h",
      "new_id": "2353521c5c8ca188108892203b330dacdc79e40c",
      "new_mode": 33188,
      "new_path": "drivers/video/pxafb.h"
    }
  ]
}