linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Gregor Jasny <gjasny@googlemail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Jaime Velasco Juan <jsagarribay@gmail.com>
Subject: Re: stk webcam driver needs DMI upside down table
Date: Sun, 08 Apr 2012 16:12:41 +0200	[thread overview]
Message-ID: <4F819CD9.7070802@redhat.com> (raw)
In-Reply-To: <4F7F1405.9000000@googlemail.com>

Hi,

On 04/06/2012 06:04 PM, Gregor Jasny wrote:
> Hello,
>
> I recently received a webcam upside down report from a ASUS Z96Fm owner.
> Usually we add the USB id and DMI information to the libv4l upside down
> table. Except for webcam drivers that can flip images in hardware. By
> looking at stk-webcam.c I see both, a hflip anf vflip parameter.
>
> Some gspca drivers handle the situation by adding a DMI table to the
> webcam driver. Would this make sense for the STK driver, too?

hehe, funny I still had an upside down report for the STK driver
(for a different model laptop) on my to-do list.

WRT your question, maybe adding a dmi table to the driver makes sense,
but first we must change its behavior away from flipping the image
by default to leaving the image upright. Which should fix things for
the Z96FM laptop this thread started with, as well as for the Asus
A3H laptop for which I've a report.

If we then get bug reports after making this change, then those will be
for laptops which actually do have the sensor upside down (which I think
we will, I assume that is the reason currently the driver is flipping by
default) and we can collect dmi info from the reporters and add *those*
to a dmi table :)

So for now I'm going to send a patch upstream to change the default
to not flip.

Regards,

Hans



      reply	other threads:[~2012-04-08 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 16:04 stk webcam driver needs DMI upside down table Gregor Jasny
2012-04-08 14:12 ` Hans de Goede [this message]

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=4F819CD9.7070802@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=gjasny@googlemail.com \
    --cc=jsagarribay@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).