linux-kernel - Re: [PATCHv2] lis3lv02d: support both one- and two-byte sensors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Feb 2009 01:21:32 +0100
From:	Giuseppe Bilotta <giuseppe.bilotta@...il.com>
To:	Éric Piel <Eric.Piel@...mplin-utc.net>
Cc:	Pavel Machek <pavel@...e.cz>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCHv2] lis3lv02d: support both one- and two-byte sensors

[removed git from the cc because that was a mistake]

On Wed, Feb 11, 2009 at 12:54 AM, Éric Piel <Eric.Piel@...mplin-utc.net> wrote:
> BTW, now that this is working. Could you double check the correct axes set
> up. In particular, is it x_inverted or y_inverted, and what about z axis...

Now that we have the 8 vs 16 bit mess sorted out, I re-checked and
there my sensor definitely has the X (first) axis inverted, so the
one-liner patch I sent at the beginning is still valid, at least as
far as my laptop is involved. It might be that different dv5 Pavilions
have different sensors though, which will make it quite harder to sort
out.

I'd be interested in hearing from the other user (the one reporting
inverted Y): rather than checking neverball, could he use plain jstest
and see if the results match the Documentation or not?

-- 
Giuseppe "Oblomov" Bilotta
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/