Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Vanish some unused 3d commands
Date: Tue, 19 Feb 2013 09:26:03 +0000	[thread overview]
Message-ID: <20130219092603.GC4683@cantiga.alporthouse.com> (raw)
In-Reply-To: <1361251111-24437-1-git-send-email-ben@bwidawsk.net>

On Mon, Feb 18, 2013 at 09:18:31PM -0800, Ben Widawsky wrote:
> i915_reg.h is messy enough without the extra stuff.
> 
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>

Would be nice if we could just discard the rest. Since we can't (damn
you GEM/DRI1) can we just move them to i915_cmd.h?

I would also keep the BLT commands, but since no one else cares to
kill off intelfb entirely, I can always reinstate them on that fateful
day.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

      reply	other threads:[~2013-02-19  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  5:18 [PATCH] drm/i915: Vanish some unused 3d commands Ben Widawsky
2013-02-19  9:26 ` Chris Wilson [this message]

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=20130219092603.GC4683@cantiga.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=ben@bwidawsk.net \
    --cc=intel-gfx@lists.freedesktop.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