From: Andrew Morton <akpm@linux-foundation.org>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: pavel@suse.cz, eric.piel@tremplin-utc.net,
linux-kernel@vger.kernel.org, palatis@gmail.com
Subject: Re: [PATCH] lis3lv02d: add axes knowledge of HP Pavilion dv5 models
Date: Tue, 10 Feb 2009 15:17:18 -0800 [thread overview]
Message-ID: <20090210151718.4a8f3421.akpm@linux-foundation.org> (raw)
In-Reply-To: <cb7bb73a0902101448h74b6b73j8307c65c4f006152@mail.gmail.com>
On Tue, 10 Feb 2009 23:48:14 +0100
Giuseppe Bilotta <giuseppe.bilotta@gmail.com> wrote:
> On Tue, Feb 10, 2009 at 10:39 PM, Giuseppe Bilotta
> <giuseppe.bilotta@gmail.com> wrote:
> > On Tue, Feb 10, 2009 at 11:10 AM, Pavel Machek <pavel@suse.cz> wrote:
> >>
> >> Yeah, that patch. Not sure what to do next... you could grab lis3
> >> manual and see if you can setup chip by hand to get better results...
> >
> > As Eric pointed out, it looks definitely like an endianness problem,
> > although there are a few strange things which are happening at the
> > same time. Is the lis3 manual available online somewhere, or can I
> > request it to the mfgr?
>
> 'k, found it on the STMicroelectronics website. Reading the doc about
> LIS3LV02DL I see that WHO_AM_I should return 3Ah, but my sensor
> returns 3Bh. I'll see if I find the correct datasheet for this one
> instead, it might have info about the differences.
>
> One thing that I noticed is that (modulo axis inversion) I'm able to
> use the sensor correctly if I set the thing to only use the high byte,
> totally discarding the lower byte:
> return *((s8*)(&hi));
> Maybe this sensor needs a different setup to return 12 instead of 8
> bits of information.
>
I've lost the plot here. I still intend to merge
lis3lv02d-add-axes-knowledge-of-hp-pavilion-dv5-models.patch into
2.6.29. Someone please stop me if that is wrong.
next prev parent reply other threads:[~2009-02-10 23:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 0:48 [PATCH] lis3lv02d: add axes knowledge of HP Pavilion dv5 models Giuseppe Bilotta
2009-02-07 14:47 ` Éric Piel
2009-02-07 23:59 ` Giuseppe Bilotta
2009-02-09 9:47 ` Pavel Machek
2009-02-09 9:53 ` Giuseppe Bilotta
2009-02-09 9:58 ` Pavel Machek
2009-02-09 11:45 ` Giuseppe Bilotta
2009-02-09 13:33 ` Giuseppe Bilotta
2009-02-10 10:10 ` Pavel Machek
2009-02-10 21:39 ` Giuseppe Bilotta
2009-02-10 22:47 ` Éric Piel
2009-02-10 22:48 ` Giuseppe Bilotta
2009-02-10 23:17 ` Andrew Morton [this message]
2009-02-10 23:22 ` Éric Piel
2009-02-10 23:17 ` Éric Piel
2009-02-10 23:34 ` Éric Piel
[not found] ` <498E46F2.1020401@gmail.com>
2009-02-09 23:37 ` Éric Piel
[not found] ` <4990DEFD.4010700@gmail.com>
2009-02-10 10:34 ` Éric Piel
2009-02-10 11:07 ` Giuseppe Bilotta
2009-02-10 12:42 ` Éric Piel
2009-02-10 20:29 ` Giuseppe Bilotta
2009-02-10 20:31 ` Giuseppe Bilotta
2009-02-10 21:28 ` Giuseppe Bilotta
2009-02-10 21:33 ` Giuseppe Bilotta
2009-02-09 9:44 ` Pavel Machek
2009-02-09 9:50 ` Giuseppe Bilotta
[not found] ` <1234191743.3156.2.camel@localhost.localdomain>
2009-02-09 16:50 ` Giuseppe Bilotta
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=20090210151718.4a8f3421.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=eric.piel@tremplin-utc.net \
--cc=giuseppe.bilotta@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=palatis@gmail.com \
--cc=pavel@suse.cz \
/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