View Single Post
Old 06-11-2019, 08:55 PM   #197
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 4,022
Karma: 18026955
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Quote:
Originally Posted by rcentros View Post
I don't know what "Neonode zForce" means
Neonode is the company, zForce is their scheme of using IR interruption for touch.

The original Nook Simple Touch exposed internal values from the driver as:
/sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/ledlevel
If I remember correctly, it actually used a TI MSP430 to do the scanning.

The Glow3 uses the NN1001 (main controller) and NN2003 (expander?) chips.
The Glow 3 had the driver here, but no usable values:
/sys/devices/platform/imx-i2c.1/i2c-1/1-0050

The values are useful as I had a little app to visualize the IR paths to help you determine where the cruft had collected in the bezel.
Renate is offline   Reply With Quote