On Wed, Oct 25, 2017 at 07:18:28PM +0300, Ville Syrjälä wrote:
> It also occurs to me that we might want to combine this fb dumper with
> the atomic state dumper. That one already prints out stuf about
> framebuffers in drm_atomic_plane_print_state(). Not sure if there
> would be a nice way to keep
On Wed, Oct 25, 2017 at 05:22:25PM +0200, Noralf Trønnes wrote:
>
> Den 25.10.2017 15.55, skrev Ville Syrjälä:
> > On Wed, Oct 25, 2017 at 02:05:02PM +0200, Noralf Trønnes wrote:
> >> Add debugfs file that dumps info about the framebuffers and its planes.
> >> Also dump info about any connected ge
Den 25.10.2017 15.55, skrev Ville Syrjälä:
On Wed, Oct 25, 2017 at 02:05:02PM +0200, Noralf Trønnes wrote:
Add debugfs file that dumps info about the framebuffers and its planes.
Also dump info about any connected gem object(s).
Signed-off-by: Noralf Trønnes
---
Changes since version 1:
- Re
On Wed, Oct 25, 2017 at 02:05:02PM +0200, Noralf Trønnes wrote:
> Add debugfs file that dumps info about the framebuffers and its planes.
> Also dump info about any connected gem object(s).
>
> Signed-off-by: Noralf Trønnes
> ---
>
> Changes since version 1:
> - Remove const in drm_gem_print() a
Add debugfs file that dumps info about the framebuffers and its planes.
Also dump info about any connected gem object(s).
Signed-off-by: Noralf Trønnes
---
Changes since version 1:
- Remove const in drm_gem_print() argument (kbuild test robot)
- Print framebuffer modifiers (Kristian Høgsberg)