History log of /drivers/gpu/drm/gma500/psb_lid.c
Revision Date Author Comments
ac0a5dd6ae764ba228ec645920b78c70cee05eb7 21-May-2012 Alan Cox <alan@linux.intel.com> gma500: Prevent endless loop in panel power up sequence

Some devices don't have a panel connected to LVDS and thus will never power up.
This patch checks the power sequence progress bits in PP_STATUS to prevent an
endless loop on such devices.

Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
25933ddeada7fe96a9900fe5f2ecf105fe4f367b 03-May-2012 Alan Cox <alan@linux.intel.com> gma500: address the lid code

We need this for Poulsbo

Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
a746092b679e6045dae91ceacb9abc6c83e38e0e 29-Nov-2011 Alan Cox <alan@linux.intel.com> gma500: do a pass over the FIXME tags

Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
89c78134cc54dff016c83367912eb055637fa50c 03-Nov-2011 Alan Cox <alan@linux.intel.com> gma500: Add Poulsbo support

This provides the specific code for Poulsbo, some of which is also used for
the later chipsets. We support the GTT, the 2D engine (for console), and
the display setup/management. We do not support 3D or the video overlays.

In theory enough public info is available to do the video overlay work
but that represents a large task.

Framebuffer X will run nicely with this but do *NOT* use the VESA X
server at the same time as KMS. With a Dell mini 10 things like Xfce4 are
nice and usable even when compositing as the CPU has a good path to the
memory.

Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>