summaryrefslogtreecommitdiffstats
path: root/drivers/staging/gma500/TODO
diff options
context:
space:
mode:
authorAlan Cox <alan@linux.intel.com>2011-02-22 14:27:58 +0000
committerGreg Kroah-Hartman <gregkh@suse.de>2011-02-23 13:37:34 -0800
commit0867b42113ec4eb8646eb361b15cbcfb741ddf5b (patch)
tree7af589f3b3599ebd36a6c4e0a3a608a8b3a3836e /drivers/staging/gma500/TODO
parent008536e8458613ce569595e43b0e71afa8b48ae8 (diff)
downloadop-kernel-dev-0867b42113ec4eb8646eb361b15cbcfb741ddf5b.zip
op-kernel-dev-0867b42113ec4eb8646eb361b15cbcfb741ddf5b.tar.gz
staging: gma500: Intel GMA500 staging driver
This is an initial staging driver for the GMA500. It's been stripped out of the PVR drivers and crunched together from various bits of code and different kernels. Currently it's unaccelerated but still pretty snappy even compositing with the frame buffer X server. Lots of work is needed to rework the ttm and bo interfaces from being ripped out and then 2D acceleration wants putting back for framebuffer and somehow eventually via DRM. There is no support for the parts without open source userspace (video accelerators, 3D) as per kernel policy. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/staging/gma500/TODO')
-rw-r--r--drivers/staging/gma500/TODO26
1 files changed, 26 insertions, 0 deletions
diff --git a/drivers/staging/gma500/TODO b/drivers/staging/gma500/TODO
new file mode 100644
index 0000000..f692ce1
--- /dev/null
+++ b/drivers/staging/gma500/TODO
@@ -0,0 +1,26 @@
+- Test on more platforms
+- Clean up the various chunks of unused code
+- Sort out the power management side. Not important for Poulsbo but
+ matters for Moorestown
+- Add Moorestown support (single pipe, no BIOS, no stolen memory,
+ some other differences)
+- Sort out the bo and ttm code to support userframe buffers and DRM
+ interfaces rather than just faking it enough for a framebuffer
+- Add 2D acceleration via console and DRM
+
+As per kernel policy and the in the interest of the safety of various
+kittens there is no support or plans to add hooks for the closed user space
+stuff.
+
+
+Why bother ?
+- Proper display configuration
+- Can be made to work on Moorestown where VESA won't
+- Works on systems where the VESA BIOS is bust or the tables are broken
+ without hacks
+- 2D acceleration
+
+Currently tested on
++ Dell Mini 10 100x600
+
+
OpenPOWER on IntegriCloud