public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [patch] add video_nr module param to gspca
Date: Mon, 12 Jan 2009 13:51:44 +0300	[thread overview]
Message-ID: <496B20C0.3090908@aknet.ru> (raw)
In-Reply-To: <20090112085103.0e84305a@free.fr>

Hi.

Jean-Francois Moine wrote:
> Looking at the video drivers, I found that only half of these ones have
> this parameter. Then, I think it should be better to remove it
> everywhere!
OK, that might be a solution too. :)

> In fact, setting the video number in the right driver before plugging
> any video device is rather complicated while setting udev rules is easy
> and has to be done only once...
No, its not like that. You only add the
strings like
options gspca video_nr=1
in your /etc/modprobe.conf, and you are
done. ALSA went even further and introduced
the option "order", so that you write:
options snd order=snd-intel8x0,snd-hda-intel
for example. So, from some point of view, this
is actually easier than the udev solution
(eg. I always did that and never played with
udev :), but indeed, having two ways of doing
the same thing is usually confusing, so I am
not trying to talk you into applying my patch. :)
If there is an intention to deprecate the "video_nr"
thing, then it certainly doesn't apply.


  parent reply	other threads:[~2009-01-12 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10 18:53 [patch] add video_nr module param to gspca Stas Sergeev
2009-01-11 19:25 ` Jean-Francois Moine
2009-01-11 20:17   ` Stas Sergeev
     [not found]     ` <20090112085103.0e84305a@free.fr>
2009-01-12 10:51       ` Stas Sergeev [this message]
2009-01-11 23:19 ` Mauro Carvalho Chehab

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=496B20C0.3090908@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=linux-media@vger.kernel.org \
    --cc=moinejf@free.fr \
    /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