From: Alan Cox <alan@linux.jf.intel.com>
To: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] Further clean up and setup
Date: Tue, 19 Apr 2011 15:26:51 +0100 [thread overview]
Message-ID: <20110419142432.16479.89255.stgit@localhost.localdomain> (raw)
This begins to put meaningful code into the buffer management. It's in theory
pretty much all there now but needs a fair bit of debug before it'll actually
do anything useful. We also strip out a lot of the old GTT code we no longer
need and the last remnants of the TTM stuff.
---
Alan Cox (8):
gma500: allow non stolen page backed framebuffer
gma500: prune some unused variables
gma500: GEM - now we have the basics we shall stick pins in it
gma500: GEMify the frame buffer base bits
gma500: Begin the GEMification of the cursor code
gma500: Add support for inserting and removing pages from the GART
gma500: begin adding GEM
gma500: add the ability to request backed space or not
drivers/staging/gma500/Makefile | 2
drivers/staging/gma500/mrst_crtc.c | 15
drivers/staging/gma500/psb_2d.c | 4
drivers/staging/gma500/psb_drm.h | 11
drivers/staging/gma500/psb_drv.c | 46 +
drivers/staging/gma500/psb_drv.h | 25 -
drivers/staging/gma500/psb_fb.c | 301 +++----
drivers/staging/gma500/psb_fb.h | 5
drivers/staging/gma500/psb_gem.c | 209 +++++
drivers/staging/gma500/psb_gtt.c | 1215 ++++++++--------------------
drivers/staging/gma500/psb_gtt.h | 70 --
drivers/staging/gma500/psb_intel_display.c | 116 +--
drivers/staging/gma500/psb_intel_drv.h | 13
drivers/staging/gma500/psb_intel_lvds.c | 14
drivers/staging/gma500/psb_powermgmt.c | 5
drivers/staging/gma500/psb_pvr_glue.c | 73 --
drivers/staging/gma500/psb_pvr_glue.h | 25 -
17 files changed, 801 insertions(+), 1348 deletions(-)
create mode 100644 drivers/staging/gma500/psb_gem.c
delete mode 100644 drivers/staging/gma500/psb_pvr_glue.c
delete mode 100644 drivers/staging/gma500/psb_pvr_glue.h
--
Carry on carry on, there's nothing to be done on days like these
In the ruins and the rage, planting flowers for new days
In the ruins and the rage, we carry on
next reply other threads:[~2011-04-19 14:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 14:26 Alan Cox [this message]
2011-04-19 14:27 ` [PATCH 1/8] gma500: add the ability to request backed space or not Alan Cox
2011-04-20 20:31 ` Greg KH
2011-04-20 21:21 ` Alan Cox
2011-04-21 5:05 ` Greg KH
2011-04-21 5:06 ` Greg KH
2011-04-21 8:49 ` Alan Cox
2011-04-26 0:15 ` Greg KH
2011-04-19 14:27 ` [PATCH 2/8] gma500: begin adding GEM Alan Cox
2011-04-19 14:27 ` [PATCH 3/8] gma500: Add support for inserting and removing pages from the GART Alan Cox
2011-04-19 14:27 ` [PATCH 4/8] gma500: Begin the GEMification of the cursor code Alan Cox
2011-04-19 14:28 ` [PATCH 5/8] gma500: GEMify the frame buffer base bits Alan Cox
2011-04-19 14:28 ` [PATCH 6/8] gma500: GEM - now we have the basics we shall stick pins in it Alan Cox
2011-04-19 14:28 ` [PATCH 7/8] gma500: prune some unused variables Alan Cox
2011-04-19 14:28 ` [PATCH 8/8] gma500: allow non stolen page backed framebuffer 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=20110419142432.16479.89255.stgit@localhost.localdomain \
--to=alan@linux.jf.intel.com \
--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