From: Jordan Crouse <jcrouse@codeaurora.org>
To: intel-gfx@lists.freedesktop.org
Cc: freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org
Subject: [RFC] Move i915 ascii85 functions to linux/ascii85.h
Date: Fri, 26 Jan 2018 13:59:21 -0700 [thread overview]
Message-ID: <1517000362-24164-1-git-send-email-jcrouse@codeaurora.org> (raw)
I've been working on a crash dump utility for the drm/msm GPU driver
to get the useful GPU information out after a hang. Taking inspiration
from the i915 driver I thought it was very smart to use ascii85 format
to encode the binary buffers and other bits. This patch moves the two
very simple functions to encode binaries as ascii85 from the i915
driver to a linux header to be enjoyed by all.
I debated if it was better to move them to drm/ or go all the way and
obviously I picked all the way, but if the owners and maintainers feel
like this is something we want to keep closer to home then by all means
lets do what feels best.
Suggestions and flames welcome. Coming immediately after will be the drm/msm
stack that uses this in anger.
Jordan Crouse (1):
include: Move ascii85 functions from i915 to linux/ascii85.h
drivers/gpu/drm/i915/i915_gpu_error.c | 24 +---------------
include/linux/ascii85.h | 52 +++++++++++++++++++++++++++++++++++
2 files changed, 53 insertions(+), 23 deletions(-)
create mode 100644 include/linux/ascii85.h
--
1.9.1
next reply other threads:[~2018-01-26 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 20:59 Jordan Crouse [this message]
2018-01-26 20:59 ` [PATCH] include: Move ascii85 functions from i915 to linux/ascii85.h Jordan Crouse
2018-01-26 21:13 ` Chris Wilson
2018-01-26 21:19 ` Chris Wilson
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=1517000362-24164-1-git-send-email-jcrouse@codeaurora.org \
--to=jcrouse@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-arm-msm@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