Home
last modified time | relevance | path

Searched hist:bc794829141f28e14fe7d0e07e35870bd9aee78c (Results 1 – 6 of 6) sorted by relevance

/linux/drivers/gpu/drm/gma500/
H A Dpsb_device.cdiff bc794829141f28e14fe7d0e07e35870bd9aee78c Mon May 21 16:27:30 CEST 2012 Patrik Jakobsson <patrik.r.jakobsson@gmail.com> gma500: handle poulsbo cursor restriction

Poulsbo needs a physical address in the cursor base register. We allocate a
stolen memory buffer and copy the cursor image provided by userspace into it.
When/If we get our own userspace driver we can map this stolen memory directly.
The patch also adds a mark in chip ops so we can identify devices that has this
requirement.

Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
H A Doaktrail_device.cdiff bc794829141f28e14fe7d0e07e35870bd9aee78c Mon May 21 16:27:30 CEST 2012 Patrik Jakobsson <patrik.r.jakobsson@gmail.com> gma500: handle poulsbo cursor restriction

Poulsbo needs a physical address in the cursor base register. We allocate a
stolen memory buffer and copy the cursor image provided by userspace into it.
When/If we get our own userspace driver we can map this stolen memory directly.
The patch also adds a mark in chip ops so we can identify devices that has this
requirement.

Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
H A Dcdv_device.cdiff bc794829141f28e14fe7d0e07e35870bd9aee78c Mon May 21 16:27:30 CEST 2012 Patrik Jakobsson <patrik.r.jakobsson@gmail.com> gma500: handle poulsbo cursor restriction

Poulsbo needs a physical address in the cursor base register. We allocate a
stolen memory buffer and copy the cursor image provided by userspace into it.
When/If we get our own userspace driver we can map this stolen memory directly.
The patch also adds a mark in chip ops so we can identify devices that has this
requirement.

Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
H A Dpsb_intel_drv.hdiff bc794829141f28e14fe7d0e07e35870bd9aee78c Mon May 21 16:27:30 CEST 2012 Patrik Jakobsson <patrik.r.jakobsson@gmail.com> gma500: handle poulsbo cursor restriction

Poulsbo needs a physical address in the cursor base register. We allocate a
stolen memory buffer and copy the cursor image provided by userspace into it.
When/If we get our own userspace driver we can map this stolen memory directly.
The patch also adds a mark in chip ops so we can identify devices that has this
requirement.

Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
H A Dpsb_intel_display.cdiff bc794829141f28e14fe7d0e07e35870bd9aee78c Mon May 21 16:27:30 CEST 2012 Patrik Jakobsson <patrik.r.jakobsson@gmail.com> gma500: handle poulsbo cursor restriction

Poulsbo needs a physical address in the cursor base register. We allocate a
stolen memory buffer and copy the cursor image provided by userspace into it.
When/If we get our own userspace driver we can map this stolen memory directly.
The patch also adds a mark in chip ops so we can identify devices that has this
requirement.

Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
H A Dpsb_drv.hdiff bc794829141f28e14fe7d0e07e35870bd9aee78c Mon May 21 16:27:30 CEST 2012 Patrik Jakobsson <patrik.r.jakobsson@gmail.com> gma500: handle poulsbo cursor restriction

Poulsbo needs a physical address in the cursor base register. We allocate a
stolen memory buffer and copy the cursor image provided by userspace into it.
When/If we get our own userspace driver we can map this stolen memory directly.
The patch also adds a mark in chip ops so we can identify devices that has this
requirement.

Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>