From: Hans de Goede <hdegoede@redhat.com>
To: Bastien Nocera <hadess@hadess.net>, linux-iio@vger.kernel.org
Subject: Re: linux-iio and Windows default orientations
Date: Tue, 12 May 2020 18:12:13 +0200 [thread overview]
Message-ID: <fad058f5-ba5c-0cf2-317f-c0bb8457846e@redhat.com> (raw)
In-Reply-To: <16f4bfe1c254798291507aca00afeb2c8b0978a7.camel@hadess.net>
Hi,
On 5/12/20 3:55 PM, Bastien Nocera wrote:
> Hey,
>
> I'm just dotting the is, and crossing the ts on a bunch of iio-sensor-
> proxy documentation and wanted to revisit the IIO documentation,
> compared to what Windows, and my implementation did.
>
> Does this:
> https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/tree/Documentation/ABI/testing/sysfs-bus-iio#n1638
> in particular the "Z" axis:
> "Z is perpendicular to the screen plane and positive out of the screen"
>
> match this:
> https://docs.microsoft.com/en-us/windows/uwp/devices-sensors/sensor-orientation
> "with the positive z-axis extending out from the device."
Yes I believe that the 2 are stating the same, this is also how the
Z axis works on Android I believe. If you put a phone or tablet
flat on a table with the display up, then you will get a -1.0G or -9.8 m/s²
reading since the gravity is pulling downwards (away from the front of
the screen) with 1G.
> This Microsoft page didn't exist when I changed the code to "match
> Windows 10" in 2016:
> https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/commit/35b6328cbdaa5efa30917c445962d64fd733fb02
>
> (And just to double check, it seems that the other 2 axis do match in
> their definitions, right?)
Yes I believe they do, and also again Android's definition.
Regards,
Hans
next prev parent reply other threads:[~2020-05-12 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 13:55 linux-iio and Windows default orientations Bastien Nocera
2020-05-12 16:12 ` Hans de Goede [this message]
2020-06-24 9:31 ` Bastien Nocera
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=fad058f5-ba5c-0cf2-317f-c0bb8457846e@redhat.com \
--to=hdegoede@redhat.com \
--cc=hadess@hadess.net \
--cc=linux-iio@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).