From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Ran Shalit <ranshalit@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: v4l2 kernel module debugging methods
Date: Thu, 10 Dec 2015 19:22:26 -0500 [thread overview]
Message-ID: <1449793346.2521.11.camel@collabora.com> (raw)
In-Reply-To: <CAJ2oMh+MG20jYdNSfXWZN+0vH2BPi_Z+v4OB-VH5ehi7qmfmpw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
Le jeudi 10 décembre 2015 à 23:46 +0200, Ran Shalit a écrit :
> Thank you for the comment.
> As someone expreinced with v4l2 device driver, do you recommened
> using
> debugging technique such as qemu (or kgdb) or do you rather use plain
> printing ?
I never used that, printing I used. You should also run v4l2-
compliance. It's a test suite, part of v4l-utils.
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-12-11 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 22:00 v4l2 kernel module debugging methods Ran Shalit
2015-12-06 0:23 ` Nicolas Dufresne
2015-12-10 21:46 ` Ran Shalit
2015-12-11 0:22 ` Nicolas Dufresne [this message]
2015-12-11 8:50 ` Fabien DESSENNE
2015-12-12 11:40 ` Ran Shalit
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=1449793346.2521.11.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=linux-media@vger.kernel.org \
--cc=ranshalit@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.