From: Adam Baker <linux@baker-net.org.uk>
To: linux-media@vger.kernel.org, kilgota@banach.math.auburn.edu,
Hans de Goede <j.w.r.degoede@hhs.nl>,
"Jean-Francois Moine" <moinejf@free.fr>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: [RFC][PATCH 0/2] Sensor orientation reporting
Date: Sun, 15 Mar 2009 22:24:28 +0000 [thread overview]
Message-ID: <200903152224.29388.linux@baker-net.org.uk> (raw)
Hi all,
I've finally got round to writing a sample patch to support the proposed
mechanism of reporting sensor orientation to user space. It is split into 2
parts, part 1 contains the kernel changes and part 2 the libv4l changes. In
order to keep the patch simple I haven't attempted to add support to libv4l
for HFLIP and VFLIP but just assumed for now that if a cam needs one then it
needs both. If the basic idea gets accepted then fixing that is purely a user
space change.
I also haven't provided an implementation of VIDIOC_ENUMINPUT in libv4l that
updates the flags to reflect what libv4l has done to the image. Hans Verkuil
originally said he wanted to leave the orientation information available to
the user app but I suspect that is actually undesirable. If an app is
designed to work without libv4l and to re-orient an image as required then if
someone runs it with the LD_PRELOAD capability of libv4l then correct
operation depends upon reporting the corrected orientation to the app, not
the original orientation.
Adam
next reply other threads:[~2009-03-15 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 22:24 Adam Baker [this message]
2009-03-15 22:29 ` [RFC][PATCH 1/2] Sensor orientation reporting Adam Baker
2009-03-27 17:31 ` Mauro Carvalho Chehab
2009-03-27 23:36 ` Adam Baker
2009-03-27 19:21 ` Jean-Francois Moine
2009-03-15 22:34 ` [RFC][PATCH 2/2] " Adam Baker
2009-03-16 8:00 ` [RFC][PATCH 0/2] " Hans de Goede
2009-03-16 18:20 ` Theodore Kilgore
2009-03-16 23:36 ` Adam Baker
2009-03-17 8:10 ` Hans de Goede
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=200903152224.29388.linux@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--cc=hverkuil@xs4all.nl \
--cc=j.w.r.degoede@hhs.nl \
--cc=kilgota@banach.math.auburn.edu \
--cc=linux-media@vger.kernel.org \
--cc=moinejf@free.fr \
/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.