From: Alan Cox <alan@linux.intel.com>
To: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: [PATCH 00/18] GMA500 updates
Date: Wed, 30 Mar 2011 09:58:57 +0100 [thread overview]
Message-ID: <20110330085539.5897.67919.stgit@localhost.localdomain> (raw)
This set of patches tackles three basic things
- Add support for Moorestown (not yet usable as it needs a memory allocator)
- Completely remove all the ttm related glue from the driver
- Turn on SDVO support on Poulsbo - which should get the various non panel
users working
Getting useful Moorestown support will need the power management tackling
further, memory allocator and possibly MIPI panel support. For now the priority
is Poulsbo.
---
Alan Cox (17):
gma500: turn on psb SDVO
gma500; kill off TTM
gma500: pull mrst firmware stuff into its own header
gma500: Clean up more unused structures and code
gma500: We don't support the CI either
gma500: delete the RAR handling
gma500: Add Moorestown identifiers
gma500: Moorestown does its setup differently
gma500: enable Moorestown CRTC handling
gma500: add framebuffer setup
gma500: Add Moorestown backlight support
gma500: Makefiles
gma500: Add moorestown specific data to the device structure
gma500: Add moorestown config structures
gma500: Make some of the lvds operations non-static
gma500: Add moorestown lvds driver code
gma500: begin adding Moorestown support
Justin P. Mattock (1):
drivers:staging:gma500 Remove extra semi-colon.
drivers/staging/gma500/Makefile | 11
drivers/staging/gma500/mrst.h | 217 ++++++++
drivers/staging/gma500/mrst_crtc.c | 623 +++++++++++++++++++++++
drivers/staging/gma500/mrst_lvds.c | 364 +++++++++++++
drivers/staging/gma500/psb_2d.c | 1
drivers/staging/gma500/psb_bl.c | 112 +++-
drivers/staging/gma500/psb_buffer.c | 450 ----------------
drivers/staging/gma500/psb_drm.h | 111 ----
drivers/staging/gma500/psb_drv.c | 543 ++++++++------------
drivers/staging/gma500/psb_drv.h | 278 +---------
drivers/staging/gma500/psb_fb.c | 23 +
drivers/staging/gma500/psb_fence.c | 122 ----
drivers/staging/gma500/psb_gtt.c | 51 --
drivers/staging/gma500/psb_gtt.h | 4
drivers/staging/gma500/psb_intel_display.c | 10
drivers/staging/gma500/psb_intel_lvds.c | 16 -
drivers/staging/gma500/psb_sgx.c | 238 ---------
drivers/staging/gma500/psb_sgx.h | 32 -
drivers/staging/gma500/psb_ttm_fence.c | 605 ----------------------
drivers/staging/gma500/psb_ttm_fence_api.h | 272 ----------
drivers/staging/gma500/psb_ttm_fence_driver.h | 302 -----------
drivers/staging/gma500/psb_ttm_fence_user.c | 237 ---------
drivers/staging/gma500/psb_ttm_fence_user.h | 140 -----
drivers/staging/gma500/psb_ttm_glue.c | 349 -------------
drivers/staging/gma500/psb_ttm_placement_user.c | 628 -----------------------
drivers/staging/gma500/psb_ttm_userobj_api.h | 85 ---
26 files changed, 1593 insertions(+), 4231 deletions(-)
create mode 100644 drivers/staging/gma500/mrst.h
create mode 100644 drivers/staging/gma500/mrst_crtc.c
create mode 100644 drivers/staging/gma500/mrst_lvds.c
delete mode 100644 drivers/staging/gma500/psb_buffer.c
delete mode 100644 drivers/staging/gma500/psb_fence.c
delete mode 100644 drivers/staging/gma500/psb_sgx.c
delete mode 100644 drivers/staging/gma500/psb_sgx.h
delete mode 100644 drivers/staging/gma500/psb_ttm_fence.c
delete mode 100644 drivers/staging/gma500/psb_ttm_fence_api.h
delete mode 100644 drivers/staging/gma500/psb_ttm_fence_driver.h
delete mode 100644 drivers/staging/gma500/psb_ttm_fence_user.c
delete mode 100644 drivers/staging/gma500/psb_ttm_fence_user.h
delete mode 100644 drivers/staging/gma500/psb_ttm_glue.c
delete mode 100644 drivers/staging/gma500/psb_ttm_placement_user.c
delete mode 100644 drivers/staging/gma500/psb_ttm_userobj_api.h
--
Alan
next reply other threads:[~2011-03-30 9:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 8:58 Alan Cox [this message]
2011-03-30 8:59 ` [PATCH 01/18] gma500: begin adding Moorestown support Alan Cox
2011-03-30 8:59 ` [PATCH 02/18] gma500: Add moorestown lvds driver code Alan Cox
2011-03-30 8:59 ` [PATCH 03/18] gma500: Make some of the lvds operations non-static Alan Cox
2011-03-30 8:59 ` [PATCH 04/18] gma500: Add moorestown config structures Alan Cox
2011-03-30 8:59 ` [PATCH 05/18] gma500: Add moorestown specific data to the device structure Alan Cox
2011-03-30 8:59 ` [PATCH 06/18] gma500: Makefiles Alan Cox
2011-03-30 9:00 ` [PATCH 07/18] gma500: Add Moorestown backlight support Alan Cox
2011-03-30 10:33 ` Matthew Garrett
2011-03-30 9:00 ` [PATCH 08/18] gma500: add framebuffer setup Alan Cox
2011-03-30 9:00 ` [PATCH 09/18] gma500: enable Moorestown CRTC handling Alan Cox
2011-03-30 9:00 ` [PATCH 10/18] gma500: Moorestown does its setup differently Alan Cox
2011-03-30 9:00 ` [PATCH 11/18] gma500: Add Moorestown identifiers Alan Cox
2011-03-30 9:00 ` [PATCH 12/18] gma500: delete the RAR handling Alan Cox
2011-03-30 9:01 ` [PATCH 13/18] gma500: We don't support the CI either Alan Cox
2011-03-30 9:01 ` [PATCH 14/18] gma500: Clean up more unused structures and code Alan Cox
2011-03-30 9:01 ` [PATCH 15/18] gma500: pull mrst firmware stuff into its own header Alan Cox
2011-03-30 9:01 ` [PATCH 16/18] gma500; kill off TTM Alan Cox
2011-03-30 9:01 ` [PATCH 17/18] drivers:staging:gma500 Remove extra semi-colon Alan Cox
2011-03-30 9:01 ` [PATCH 18/18] gma500: turn on psb SDVO Alan Cox
2011-03-30 10:35 ` [PATCH 00/18] GMA500 updates Matthew Garrett
2011-03-30 10:23 ` 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=20110330085539.5897.67919.stgit@localhost.localdomain \
--to=alan@linux.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