dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: dri-devel@lists.sourceforge.net
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PATCH 0/5] clean up radeon_asic.h v2
Date: Thu, 11 Mar 2010 22:19:13 +0100	[thread overview]
Message-ID: <1268342358-7532-1-git-send-email-daniel.vetter@ffwll.ch> (raw)

Hi all,

All new patch pile to make radeon_asic.h into a real header file. Now all
the asic structs are gathered in the new radeon_asic.c file.

Tested on my rv570.

I've also added a new patch that gathers all r100 specific declarations
into radeon_asic.h (at least where it makes sense). This is just an example
to convince Jerome that radeon_asic.h might not be totally useless ;)

Again, comments higly welcome.

Yours, Daniel

Daniel Vetter (5):
  drm/radeon: create radeon_asic.c
  drm/radeon: move asic structs to radeon_asic.c
  drm/radeon: unconfuse return value of radeon_asic->clear_surface_reg
  drm/radeon: include radeon_asic.h in the asic specific files
  drm/radeon: collect r100 asic related declarations in radeon_asic.h

 drivers/gpu/drm/radeon/Makefile        |    2 +-
 drivers/gpu/drm/radeon/evergreen.c     |    1 +
 drivers/gpu/drm/radeon/r100.c          |    1 +
 drivers/gpu/drm/radeon/r200.c          |    1 +
 drivers/gpu/drm/radeon/r300.c          |    1 +
 drivers/gpu/drm/radeon/r420.c          |    1 +
 drivers/gpu/drm/radeon/r520.c          |    1 +
 drivers/gpu/drm/radeon/r600.c          |    1 +
 drivers/gpu/drm/radeon/radeon.h        |   55 +---
 drivers/gpu/drm/radeon/radeon_asic.c   |  723 ++++++++++++++++++++++++++++++++
 drivers/gpu/drm/radeon/radeon_asic.h   |  545 +++----------------------
 drivers/gpu/drm/radeon/radeon_device.c |  199 ---------
 drivers/gpu/drm/radeon/rs400.c         |    1 +
 drivers/gpu/drm/radeon/rs600.c         |    1 +
 drivers/gpu/drm/radeon/rs690.c         |    1 +
 drivers/gpu/drm/radeon/rv515.c         |    1 +
 drivers/gpu/drm/radeon/rv770.c         |    1 +
 17 files changed, 793 insertions(+), 743 deletions(-)
 create mode 100644 drivers/gpu/drm/radeon/radeon_asic.c


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

             reply	other threads:[~2010-03-11 21:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 21:19 Daniel Vetter [this message]
2010-03-11 21:19 ` [PATCH 1/5] drm/radeon: create radeon_asic.c Daniel Vetter
2010-03-11 21:19 ` [PATCH 2/5] drm/radeon: move asic structs to radeon_asic.c Daniel Vetter
2010-03-11 21:19 ` [PATCH 3/5] drm/radeon: unconfuse return value of radeon_asic->clear_surface_reg Daniel Vetter
2010-03-11 21:19 ` [PATCH 4/5] drm/radeon: include radeon_asic.h in the asic specific files Daniel Vetter
2010-03-11 21:19 ` [PATCH 5/5] drm/radeon: collect r100 asic related declarations in radeon_asic.h Daniel Vetter
2010-03-12  9:25 ` [PATCH 0/5] clean up radeon_asic.h v2 Jerome Glisse
2010-03-12  9:48   ` Daniel Vetter
2010-03-15  1:33     ` Dave Airlie

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=1268342358-7532-1-git-send-email-daniel.vetter@ffwll.ch \
    --to=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).