linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: jic23@jic23.retrosnub.co.uk
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: bmc150_accel i2c-BMA250E:00: Invalid chip f8
Date: Thu, 23 Jul 2015 17:22:25 +0200	[thread overview]
Message-ID: <1437664945.2863.14.camel@hadess.net> (raw)
In-Reply-To: <20150723135953.77FEB431C5@saturn.retrosnub.co.uk>

On Thu, 2015-07-23 at 14:59 +0100, jic23@jic23.retrosnub.co.uk wrote:
> 
<snip>
> Odd. The bma250e is documented as having an id of 0xf9 not 0xf8.
> http://ae-bst.resource.bosch.com/media/products/dokumente/bma250e/BST
> -BMA250 
> E-DS004-05_published.pdf 
> 
> So all I can think of is that the chip is a bma222e (or something 
> else
> with the 0xf8 chip id) or there are some bma250e's out there with
> the wrong ID... 
> 
> Someone changed a part on the device and thought no one would notice
> and hence didn't update the bios? (even if it has a totally different
> range) 
> 
> I guess if you frig the driver to load anyway we can see what value
> it is giving for g and that should give us more of a clue. 

I've sent 1 preparation patch, and one fixup patch to ignore the
ACPI/I2C ID when selecting the chip type.

Cheers


      parent reply	other threads:[~2015-07-23 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 18:48 bmc150_accel i2c-BMA250E:00: Invalid chip f8 Bastien Nocera
2015-07-23  9:37 ` Tirdea, Irina
2015-07-23  9:41   ` Bastien Nocera
2015-07-23 13:59 ` jic23
2015-07-23 14:01   ` jic23
2015-07-23 15:22   ` Bastien Nocera [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=1437664945.2863.14.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=jic23@jic23.retrosnub.co.uk \
    --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).