Hi David,
> Yes, the patch you sent (switching to "method 3" to work around the
> evident bug in the i2c-ixp3xx driver) works on the platform I was
> using too (after unrelated tweaks).
> Here's an updated patch, using "method 3". If it still behaves
> for you, it'd seem ready to merge...
Hi David,
Yes, the patch you sent (switching to method 3 to work around the
evident bug in the i2c-ixp3xx driver) works on the platform I was
using too (after unrelated tweaks).
Here's an updated patch, using method 3. If it still behaves
for you, it'd seem ready to merge...
Works fine,
> On Sunday 10 December 2006 10:27 pm, Voipio Riku wrote:
>> > Update the rtc-rs5c372 driver:
>> > I suspect the
>> > issue wasn't that "mode 1" didn't work on that board; the original
>> > code to fetch the trim was broken. If "mode 1&
On Sunday 10 December 2006 10:27 pm, Voipio Riku wrote:
Update the rtc-rs5c372 driver:
I suspect the
issue wasn't that mode 1 didn't work on that board; the original
code to fetch the trim was broken. If mode 1 really won't work,
that's almost certainly a bug in that board's I2C driver
> Update the rtc-rs5c372 driver:
> I suspect the
> issue wasn't that "mode 1" didn't work on that board; the original
> code to fetch the trim was broken. If "mode 1" really won't work,
> that's almost certainly a bug in that board's I2C driver.
It was not related to trim fetching. Yes, it very
Update the rtc-rs5c372 driver:
I suspect the
issue wasn't that mode 1 didn't work on that board; the original
code to fetch the trim was broken. If mode 1 really won't work,
that's almost certainly a bug in that board's I2C driver.
It was not related to trim fetching. Yes, it very likely
6 matches
Mail list logo
