From: Daniel Vetter <daniel@ffwll.ch>
To: Eugeni Dodonov <eugeni@dodonov.net>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] Add tools/intel_infoframes
Date: Mon, 9 Jan 2012 17:59:05 +0100 [thread overview]
Message-ID: <20120109165905.GH3723@phenom.ffwll.local> (raw)
In-Reply-To: <CAC7LmntHgNETjR0O4Fi4znSphzD4hXSEhN6ochvrW4RA0fTygA@mail.gmail.com>
On Mon, Jan 09, 2012 at 12:42:06PM -0200, Eugeni Dodonov wrote:
> On Mon, Jan 9, 2012 at 12:03, <przanoni@gmail.com> wrote:
>
> > From: Paulo Zanoni <paulo.r.zanoni@intel.com>
> >
> > This is a command-line tool that allows us to display and modify the
> > InfoFrames we send.
> >
> > Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> >
>
> Very interesting!
>
> I think that it would be more interesting to use command line options
> instead of interactive input - something like:
> -d, --dump
> -c, --change [parameters]
> -dd, --dip-disable
> -de, --dip-enable [parameters]
> -hd, --hdmi-disable
> -he, --hdmi-enable [parameters]
>
> So this could be scripted and used non-interactively. This would also
> simplify your change_avi_infoframe and parse_infoframe_option_s - you could
> just pass all the values as parameters instead.
I like Eugeni's suggestion - all our other dump/decode/fiddle with the hw
tools are non-interactive (safe only for intel_gpu_top iirc). Can I bother
you to do this?
Yours, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-01-09 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 14:03 [PATCH] Add tools/intel_infoframes przanoni
2012-01-09 14:42 ` Eugeni Dodonov
2012-01-09 16:59 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-13 13:27 Paulo Zanoni
2012-04-13 13:49 ` Daniel Vetter
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=20120109165905.GH3723@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=eugeni@dodonov.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.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.