public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Joerg Heckenbach <joerg@heckenbach-aw.de>,
	Dwaine Garden <dwainegarden@rogers.com>,
	linux-media@vger.kernel.org,
	Kernel development list <linux-kernel@vger.kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [PATCH] [resend] usbvision: disable scaling for Nogatech MicroCam
Date: Fri, 22 Jul 2011 23:44:39 +0200	[thread overview]
Message-ID: <201107222344.46003.linux@rainbow-software.org> (raw)
In-Reply-To: <CAGoCfiyGUR7-aPqoFOHW=DkBNxav+=34np68ZPutdQWcU4GO=A@mail.gmail.com>

On Friday 22 July 2011 23:31:46 Devin Heitmueller wrote:
> On Fri, Jul 22, 2011 at 5:22 PM, Ondrej Zary <linux@rainbow-software.org> wrote:
> > Seems that this bug is widespread - the same problem appears also in guvcview
> > and adobe flash. I think that the driver is broken too - it should return
> > corrected resolution in TRY_FMT.
> 
> Well, if the driver does not return the resolution it is actually
> capturing in, then that indeed is a driver bug.  That's a different
> issue though than what your patch proposed.
> 
> You should make the TRY_FMT call specifying an invalid resolution and
> see if it returns the real resolution the device will capture at.  If
> it doesn't, then fix *that* bug.

It does not, there's no code that would do that. I actually fixed that only
to find out that the scaling is unusable at least with the MicroCam because
of black horizontal lines that appear in the image (amount of the lines
depend on the scaling factor). So I just disabled the scaling completely for
MicroCam.

I also don't know if the multiple-of-64 width limit is valid for all
usbvision devices - that's why I haven't posted patch to fix this.

> The application needs to know the capturing resolution, so it's
> possible that it does properly handle the driver passing back the real
> resolution and the driver is at fault, in which case no change is
> needed to the app at all.
> 
> Devin
> 



-- 
Ondrej Zary

  reply	other threads:[~2011-07-22 21:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 20:00 [PATCH] [resend] usbvision: disable scaling for Nogatech MicroCam Ondrej Zary
2011-07-22 20:06 ` Devin Heitmueller
2011-07-22 21:22   ` Ondrej Zary
2011-07-22 21:31     ` Devin Heitmueller
2011-07-22 21:44       ` Ondrej Zary [this message]
2011-07-27 15:03         ` Mauro Carvalho Chehab
2011-08-01 18:50           ` Ondrej Zary
2011-08-01 20: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=201107222344.46003.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=dheitmueller@kernellabs.com \
    --cc=dwainegarden@rogers.com \
    --cc=hverkuil@xs4all.nl \
    --cc=joerg@heckenbach-aw.de \
    --cc=linux-kernel@vger.kernel.org \
    --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