From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] gma500: Update the TODO list
Date: Tue, 05 Jul 2011 18:45:28 +0100 [thread overview]
Message-ID: <20110705174527.28250.53338.stgit@localhost.localdomain> (raw)
From: Alan Cox <alan@linux.intel.com>
This is now horribly out of date
Signed-off-by: Alan Cox <alan@linux.intel.com>
---
drivers/staging/gma500/TODO | 29 +++++++++--------------------
1 files changed, 9 insertions(+), 20 deletions(-)
diff --git a/drivers/staging/gma500/TODO b/drivers/staging/gma500/TODO
index f692ce1..fc83615 100644
--- a/drivers/staging/gma500/TODO
+++ b/drivers/staging/gma500/TODO
@@ -1,26 +1,15 @@
-- 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
+ matters for Moorestown/Medfield
+- Debug Oaktrail/Moorestown support (single pipe, no BIOS on mrst,
+ some other differences)
- Add 2D acceleration via console and DRM
+- Add scrolling acceleration using the GTT to do remapping on the main
+ framebuffer.
+- HDMI testing
+- Oaktrail HDMI and other features
+- Oaktrail MIPI
+- Medfield needs a lot of further love
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
-
-
next reply other threads:[~2011-07-05 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 17:45 Alan Cox [this message]
2011-07-05 17:45 ` [PATCH 2/2] gma500: oops.. thou shalt stg add Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110705174527.28250.53338.stgit@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome