> On May 31, 2018, at 9:34 PM, Jason Thorpe <thor...@me.com> wrote: > > I spent some time reviewing NXP’s i2c spec this evening (well, during > timeouts, etc. — GO DUBS), and I’m becoming convinced that there is a subtle > error in our i2c_bitbang code… *smacks forehead* … RPI, of course, has a “smart” i2c controller. There may be a bug in that driver. What I should do is try gpioiic to see if the “quick read” method works there. Same caveat as below applies, however. > (Not sure I'll get to it this weekend, though… despite my kid’s spring soccer > season being finished, I seem to have a full calendar nonetheless…) -- thorpej
- Re: i2c and indirect vs. direct config Jason Thorpe
- Re: i2c and indirect vs. direct config Greg Troxel
- Re: i2c and indirect vs. direct config Mouse
- Re: i2c and indirect vs. direct config Brad Spencer
- Re: i2c and indirect vs. direct confi... Jason Thorpe
- Re: i2c and indirect vs. direct ... Brad Spencer
- Re: i2c and indirect vs. dir... Jason Thorpe
- Re: i2c and indirect vs. dir... Brad Spencer
- Re: i2c and indirect vs. dir... Jason Thorpe
- Re: i2c and indirect vs. dir... Jason Thorpe
- Re: i2c and indirect vs. dir... Jason Thorpe
- Re: i2c and indirect vs. dir... Brad Spencer
- Re: i2c and indirect vs. dir... Paul Goyette
- Re: i2c and indirect vs. dir... Jason Thorpe
- Re: i2c and indirect vs. dir... Jason Thorpe
- Re: i2c and indirect vs. dir... Paul Goyette
- Re: i2c and indirect vs. dir... Paul Goyette
- Re: i2c and indirect vs. dir... Jason Thorpe
- Re: i2c and indirect vs. dir... Thor Lancelot Simon
- Re: i2c and indirect vs. dir... Jason Thorpe
- Re: i2c and indirect vs. dir... Jason Thorpe