From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH libdrm] modetest: Allow the user to specify the plane ID
Date: Fri, 7 Oct 2016 19:51:29 +0300 [thread overview]
Message-ID: <20161007165128.GX4329@intel.com> (raw)
In-Reply-To: <CACvgo51MMWaM6HdCh1Ltq1Sv3jxzWsT+9BUAf5fAxyuz=VzD0g@mail.gmail.com>
On Thu, Oct 06, 2016 at 02:49:34PM +0100, Emil Velikov wrote:
> On 28 September 2016 at 15:27, <ville.syrjala@linux.intel.com> wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Devices can have multiple planes, so allow the user to choose between
> > them.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> In the long term I'm wondering if we don't want to nuke/deprecate the
> clunky modetest and use a slimmed down atomic one.
>
> Either way, the patch is great but we want to update modeprint to
> provide plane(s) info. Otherwise one has no way of knowing which
> plane_id to feed without explicit knowledge about the driver/hardware.
There's a modeprint? I wonder how that differs from modetest's output?
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-10-07 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 14:27 [PATCH libdrm] modetest: Allow the user to specify the plane ID ville.syrjala
2016-10-06 13:49 ` Emil Velikov
2016-10-07 16:51 ` Ville Syrjälä [this message]
2016-12-21 9:48 ` Ville Syrjälä
2016-12-24 13:39 ` Emil Velikov
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=20161007165128.GX4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@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.