linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: housegregory299 <housegregory299@gmail.com>
To: linux-media@vger.kernel.org
Subject: Re: Genuis Emessenger 310 webcam slow work with pac7302 in 2.6.37.1 kernel
Date: Sun, 27 Feb 2011 18:42:03 +0600	[thread overview]
Message-ID: <1298810523.4788.2.camel@debian> (raw)
In-Reply-To: <1298810271.4400.43.camel@debian>

В Вск, 27/02/2011 в 18:37 +0600, housegregory299 пишет:
> > As I understand the webcam was not working properly even using 2.6.32
> > kernel.
> 
> Yes, this is so. But in near installed Windows 7 webcam also work slow
> and picture quality is worse  than on Debian with 2.6.37. I think my
> webcam very limited functionality. I have to keep both the kernels on my
> system - 2.6.32 and 2.6.37 and switch between them on the need.  
> 
> > Are you using v4l2ucp for setting exposure value? This command is
> > available
> > from the v4l2ucp Debian package. Are the other controls working
> > properly?
> 
> I use v4l2ucp from command line to saving and loading webcam's
> customised parameters, (v4l2ucp -s .webcam and v4l2ucp -l .webcam)
> but with other keys are not used. All parameters in Guvcview work fine
> and properly, except Exposure. 
> 
> > Some more hints for the trying the "test images": make sure that
> > v4l-utils
> > Debian package is installed ("apt-get install v4l-utils" as root).
> > Then
> > you can use the command "v4l2-dbg --set-register=0x72 x" where "x" is
> > any
> > number between 0 and 15. This command has to be executed as root. To
> > return
> > to the normal operation just use the zero value for x. I'm not sure
> > that
> > these test patterns will work for your webcam model also, but it would
> > be
> > interesting to try.
> 
> command "v4l2-dbg --set-register=0x72 10 not help to me: With value 0
> output are similar:
> 
> root@debian:/home/t800# v4l2-dbg --set-register=0x72 10
> Failed to set register 0x00000072 value 0xa: Invalid argument
> 
> But i try setup my webcam with v4l-utils.
> 
> > The main problem is that the manufacturer of the chip which is
> > included
> > in your webcam neither released programming documentation nor
> > implemented
> > a standard protocol like USB Video Class. Without documentation open
> > source
> > projects can only use trial and error
> > ( http://en.wikipedia.org/wiki/Trial_and_error ).
> 
> I understand, OK. So.. Which webcam is better suited for Linux systems -
> UVC standard ? This is open? or closed? Sorry, if this question is wrong
> - i don't know which webcam select for my Linux-system.
> 
> > I would strongly recommend to add the mailing list
> > "linux-media@vger.kernel.org"
> > in CC field, so more people can see this conversation. 
> 
> OK. I do it 



  parent reply	other threads:[~2011-02-27 12:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1298718695.2178.30.camel@debian>
     [not found] ` <4D693EB3.6080302@freemail.hu>
     [not found]   ` <1298762810.2022.54.camel@debian>
2011-02-27 12:41     ` Genuis Emessenger 310 webcam slow work with pac7302 in 2.6.37.1 kernel housegregory299
     [not found]     ` <4D6A018E.7090404@freemail.hu>
     [not found]       ` <1298810271.4400.43.camel@debian>
2011-02-27 12:42         ` housegregory299 [this message]
2011-02-27 12:42 ` housegregory299

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=1298810523.4788.2.camel@debian \
    --to=housegregory299@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).