All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: kilgota@banach.math.auburn.edu, Hans Verkuil <hverkuil@xs4all.nl>,
	Adam Baker <linux@baker-net.org.uk>,
	linux-media@vger.kernel.org,
	Jean-Francois Moine <moinejf@free.fr>,
	Olivier Lorin <o.lorin@laposte.net>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-omap@vger.kernel.org
Subject: Re: [RFC] How to pass camera Orientation to userspace
Date: Sun, 22 Feb 2009 23:54:42 +0100	[thread overview]
Message-ID: <49A1D7B2.5070601@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0902221419550.24268@shell2.speakeasy.net>



Trent Piepho wrote:
> On Sun, 22 Feb 2009, Hans de Goede wrote:
>> Yes that is what we are talking about, the camera having a gravity switch
>> (usually nothing as advanced as a gyroscope). Also the bits we are talking
>> about are in a struct which communicates information one way, from the camera
>> to userspace, so there is no way to clear the bits to make the camera do something.
> 
> First, I'd like to say I agree with most that the installed orientation of
> the camera sensor really is a different concept than the current value of a
> gravity sensor.  It's not necessary, and maybe not even desirable, to
> handle them in the same way.
> 
> I do not see the advantage of using reserved bits instead of controls.
> 
> The are a limited number of reserved bits.  In some structures there are
> only a few left.  They will run out.  Then what?  Packing non-standard
> sensor attributes and camera sensor meta-data into a few reserved bits is
> not a sustainable policy.
> 
> Controls on the other card are not limited and won't run out.
> 

Yes but these things are *not* controls, end of discussion. The control API is 
for controls, not to stuff all kind of cruft in.

Regards,

Hans

  reply	other threads:[~2009-02-22 22:56 UTC|newest]

Thread overview: 39+ 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-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 [this message]
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
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=49A1D7B2.5070601@redhat.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.