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:	Mon, 16 Sep 2013 12:18:05 +0200
From:	Denis CIOCCA <denis.ciocca@...com>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Jonathan Cameron <jic23@...nel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"jic23@....ac.uk" <jic23@....ac.uk>,
	"arnd@...db.de" <arnd@...db.de>,
	"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
	"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>
Subject: Re: [PATCH 38/38] iio: magn-core: st: Provide support for the
 LSM303DLH

Hi Lee,

> The driver mentions that the first group of sensors have a WAI of 
> 0x3c: #define ST_MAGN_1_WAI_EXP 0x3c And when I print out the WAI read 
> from the device: Requested device: lsm303dlh_magn - read WAI: 0x3c I 
> guess I could have been lied to again by the board's datasheet again 
> and the attached device isn't actually a LSM303DLH, but how can I tell 
> for sure? 
On LSM303DLH you have to read 0x0a 0x0b and 0x0c registers, you have to 
find 0x48, 0x34 and 0x33. I think in the snowball there is the LSM303DLHC.

Denis

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ