public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Kaiser <v4l@kaiser-linux.li>
To: kilgota@banach.math.auburn.edu
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	Adam Baker <linux@baker-net.org.uk>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org,
	Jean-Francois Moine <moinejf@free.fr>,
	Hans de Goede <hdegoede@redhat.com>,
	Olivier Lorin <o.lorin@laposte.net>,
	Trent Piepho <xyzzy@speakeasy.org>,
	linux-omap@vger.kernel.org
Subject: Re: [RFC] How to pass camera Orientation to userspace
Date: Wed, 25 Feb 2009 14:11:11 +0100	[thread overview]
Message-ID: <49A5436F.8000908@kaiser-linux.li> (raw)
In-Reply-To: <alpine.LNX.2.00.0902242341070.15857@banach.math.auburn.edu>

 >> Actually, this happens and is happening!

I got OT. I just needed to vent!

Sorry for the spam.

For the sensor mounting, I think the cam knows how the sensor is mounted 
and therefor the driver knows (driver -> first abstraction layer between 
software and hardware). Therefor the drive has to report the sensor 
orientation to user space (read only).

Thomas

PS: May be, I am OT all ready.



  reply	other threads:[~2009-02-25 13:11 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18  0:30 [RFC] How to pass camera Orientation to userspace Adam Baker
2009-02-18  2:10 ` DongSoo(Nathaniel) Kim
2009-02-18 14:36   ` Hans de Goede
2009-02-18 20:45     ` Dongsoo Kim
2009-02-21 11:53 ` Hans Verkuil
2009-02-22 11:17   ` Hans de Goede
2009-02-22 11:53     ` Hans Verkuil
2009-02-22 12:21       ` Hans de Goede
2009-02-22 18:42     ` kilgota
2009-02-22 18:58       ` Hans de Goede
2009-02-22 20:01         ` kilgota
2009-02-22 21:57           ` Hans de Goede
2009-02-22 22:47             ` kilgota
2009-02-22 22:51             ` Trent Piepho
2009-02-22 22:54               ` Hans de Goede
2009-02-22 23:12                 ` Trent Piepho
2009-02-22 23:27                   ` Hans de Goede
2009-02-23  0:19                     ` Trent Piepho
2009-02-23  8:23                       ` Hans de Goede
2009-02-22 23:24                 ` Hans Verkuil
2009-02-22 23:56                   ` Trent Piepho
2009-02-23  7:34                     ` Hans Verkuil
2009-02-23 11:30                       ` Mauro Carvalho Chehab
2009-02-22 21:46         ` Adam Baker
2009-02-23 11:07   ` Mauro Carvalho Chehab
2009-02-23 22:37     ` Adam Baker
2009-02-24  0:51       ` kilgota
2009-02-24 20:23         ` Mauro Carvalho Chehab
2009-02-25  0:38           ` kilgota
2009-02-25  0:53             ` Mauro Carvalho Chehab
2009-02-25  2:12               ` kilgota
2009-02-25  3:16                 ` Mauro Carvalho Chehab
2009-02-25  6:27                   ` kilgota
2009-02-25  3:03               ` Thomas Kaiser
2009-02-25  6:19                 ` kilgota
2009-02-25 13:11                   ` Thomas Kaiser [this message]
2009-02-25  7:40               ` Hans de Goede
2009-03-01 23:45                 ` [PATCH] libv4lconvert support for SQ905C decompression kilgota

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=49A5436F.8000908@kaiser-linux.li \
    --to=v4l@kaiser-linux.li \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=kilgota@banach.math.auburn.edu \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@baker-net.org.uk \
    --cc=mchehab@infradead.org \
    --cc=moinejf@free.fr \
    --cc=o.lorin@laposte.net \
    --cc=xyzzy@speakeasy.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