linux-kernel - Re: [PATCH 2/2] docs: media: Debugging guide for the media subsystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87h68i22ww.fsf@trenco.lwn.net>
Date: Thu, 07 Nov 2024 13:40:31 -0700
From: Jonathan Corbet <corbet@....net>
To: Sebastian Fricke <sebastian.fricke@...labora.com>
Cc: bagasdotme@...il.com, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
 laurent.pinchart@...asonboard.com, hverkuil-cisco@...all.nl,
 mauro.chehab@...ux.intel.com, kernel@...labora.com,
 bob.beckett@...labora.com, nicolas.dufresne@...labora.com, Sebastian
 Fricke <sebastian.fricke@...labora.com>
Subject: Re: [PATCH 2/2] docs: media: Debugging guide for the media subsystem

Sebastian Fricke <sebastian.fricke@...labora.com> writes:

> Provide a guide for developers on how to debug code with a focus on the
> media subsystem. This document aims to provide a rough overview over the
> possibilities and a rational to help choosing the right tool for the
> given circumstances.
>
> Signed-off-by: Sebastian Fricke <sebastian.fricke@...labora.com>
> ---
>  Documentation/process/debugging/index.rst          |   1 +
>  .../debugging/media_specific_debugging_guide.rst   | 178 +++++++++++++++++++++
>  2 files changed, 179 insertions(+)

Mostly overall comments here

- much of what's here seems redundant with your other new documents; you
  seem to be going over the same list of tools?  Why not just talk about
  the ones that are unique to the media subsystem?

- Please use the function() convention throughout.

- Back in the ancient past when I was writing V4L2 drivers, one of my
  biggest problems was figuring out why applications weren't getting
  what they expected.  The vivi driver was most useful for finding
  subtle differences...  One would use vivid now, but I suspect the
  utility remains.

Thanks,

jon