public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: video4linux-list@redhat.com
Subject: Re: CONFIG_VIDEO_ADV_DEBUG question
Date: Tue, 29 Jul 2008 20:22:55 +0200	[thread overview]
Message-ID: <488F5FFF.8030306@hhs.nl> (raw)
In-Reply-To: <1217353033.1692.14.camel@localhost>

Jean-Francois Moine wrote:
> On Tue, 2008-07-29 at 14:10 +0200, Hans Verkuil wrote:
>> Hans de Goede wrote:
>>> CONFIG_VIDEO_ADV_DEBUG enables additional debugging output in the gscpa
>>> driver, which then becomes "active" when a module option gets passed. So
>> 	[snip]
>> But the way gspca uses it is not correct. I would remove the test on
>> CONFIG_VIDEO_ADV_DEBUG there altogether, or replace it with a test of a
> 
> Hello Hans and Hans,
> 
> OK. So I see 3 options:
> 1) add a new kernel config option, say CONFIG_GSPCA_DEBUG,
> 2) always set an internal compile option GSPCA_DEBUG,
> 3) have the option GSPCA_DEBUG, but unset by default.
> 
> Which is the best for you, Hans (de Goede)?
> 

My vote goes to 2, so that when users using distro kernels (which will soon 
have gspca v2, Fedora's development kernel already has it) we can tell them to 
add the necessary module option and get debug output from them without them 
having to rebuild a kernel (module).

Regards,

Hans

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-07-29 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 12:10 CONFIG_VIDEO_ADV_DEBUG question Hans Verkuil
2008-07-29 17:37 ` Jean-Francois Moine
2008-07-29 18:22   ` Hans de Goede [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-29 10:25 Hans de Goede

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=488F5FFF.8030306@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=moinejf@free.fr \
    --cc=video4linux-list@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox