From: Pavel Machek <pavel@suse.cz>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: ?ric Piel <Eric.Piel@tremplin-utc.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2] lis3lv02d: support both one- and two-byte sensors
Date: Mon, 9 Feb 2009 00:49:46 +0100 [thread overview]
Message-ID: <20090208234946.GB1415@ucw.cz> (raw)
In-Reply-To: <cb7bb73a0902101621r56224b46id9ab59dfe9501e3c@mail.gmail.com>
On Wed 2009-02-11 01:21:32, Giuseppe Bilotta wrote:
> [removed git from the cc because that was a mistake]
>
> On Wed, Feb 11, 2009 at 12:54 AM, Éric Piel <Eric.Piel@tremplin-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?
Actuall 'watch cat position' is simplest way to test it.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-02-12 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1234309249-13672-1-git-send-email-giuseppe.bilotta@gmail.com>
2009-02-10 23:46 ` Éric Piel
2009-02-10 23:51 ` Giuseppe Bilotta
2009-02-10 23:54 ` Éric Piel
2009-02-11 0:21 ` Giuseppe Bilotta
2009-02-08 23:49 ` Pavel Machek [this message]
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=20090208234946.GB1415@ucw.cz \
--to=pavel@suse.cz \
--cc=Eric.Piel@tremplin-utc.net \
--cc=giuseppe.bilotta@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®