All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Simon Ser <contact@emersion.fr>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: document DRM_IOCTL_MODE_GETFB2
Date: Mon, 15 Nov 2021 15:20:12 +0100	[thread overview]
Message-ID: <YZJsnNBc4w15Teva@phenom.ffwll.local> (raw)
In-Reply-To: <K23DZgTtMERkTEFRX3ZTohvEJ4DCdbJ3uj7rCmQC2Hh8n5z3mOioMVz4Q6TxxJjgVPao9H2RRTBL1NuCsDOCmJhrD0VelHPwqW6AhsbS7dA=@emersion.fr>

On Mon, Nov 15, 2021 at 12:09:47PM +0000, Simon Ser wrote:
> On Thursday, November 11th, 2021 at 12:50, Daniel Stone <daniel@fooishbar.org> wrote:
> 
> > In fairness it is perfectly clear, it's just that I never considered
> > calling it without master/admin because why would you ever do that?
> 
> FWIW, drm_info does it to display the current buffers metadata. Pretty
> useful when debugging.

We also have the state debugfs file for this, which should dump everything
we can decode. If it doesn't we should extend it there ideally, instead of
hand-rolling some tool that users/devs then don't have handy. debugfs
tends to be there (at least for developers).
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2021-11-15 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09  8:56 [PATCH] drm: document DRM_IOCTL_MODE_GETFB2 Simon Ser
2021-11-09  9:24 ` Daniel Vetter
2021-11-09  9:29   ` Simon Ser
2021-11-09  9:55     ` Daniel Vetter
2021-11-11  9:46   ` Pekka Paalanen
2021-11-11 11:50 ` Daniel Stone
2021-11-15 12:09   ` Simon Ser
2021-11-15 14:20     ` Daniel Vetter [this message]
2021-11-15 14:31       ` Simon Ser

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=YZJsnNBc4w15Teva@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=contact@emersion.fr \
    --cc=dri-devel@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 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.