All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ben Widawsky <ben@bwidawsk.net>, Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] Add intel_panel_fitter tool
Date: Fri, 03 Feb 2012 19:12:47 +0000	[thread overview]
Message-ID: <e39f63$3ir9j0@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <4F2C29D6.2000804@bwidawsk.net>

On Fri, 03 Feb 2012 10:39:18 -0800, Ben Widawsky <ben@bwidawsk.net> wrote:
> On 02/03/12 08:44, Paulo Zanoni wrote:
> > 2012/2/3 Chris Wilson<chris@chris-wilson.co.uk>:
> >> I don't this should an installable tool for use by end-users. Direct
> >> register access from userspace to registers that the driver owns? I'm
> >> wary of installing even root-only tools that can screw us over in
> >> unpredictable ways.
> >> -Chris
> >
> > My idea is to write a patch that adds kernel peroperties to solve
> > this, but while people still don't have kernel 3.4, the tool would be
> > useful.
> >
> > If adding this tool to i-g-t is not a good idea, that's fine too: I
> > still plan to write the kernel patches, so people wanting overscan
> > compensation will have to use the kernel patch instead of the tool.
> 
> I didn't read that email from Chris as don't add it. I read it as,
> don't have it installed if they do make install or something. So I
> think he should clarify himself. If this benefits end users now - I'm
> all for it.

As Ben said, I meant that I view this a debug/development tool and not
the final end-user solution. I think it is useful to distribute such
tools in i-g-t so that we can have testers, but I don't want it packaged
by distributions and used as the preferred/correct mode of operation.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

      reply	other threads:[~2012-02-03 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 15:09 [PATCH] Add intel_panel_fitter tool Paulo Zanoni
2012-02-03 16:37 ` Chris Wilson
2012-02-03 16:44   ` Paulo Zanoni
2012-02-03 18:39     ` Ben Widawsky
2012-02-03 19:12       ` 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='e39f63$3ir9j0@fmsmga002.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=ben@bwidawsk.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=przanoni@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.