Thread (25 messages) 25 messages, 3 authors, 2010-04-26

Re: [PATCH 10/11] viafb: rework the I2C support in the VIA framebuffer

From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Date: 2010-04-24 10:47:43
Also in: lkml

Florian Tobias Schandinat schrieb:
Jonathan Corbet schrieb:
quoted
On Sat, 24 Apr 2010 00:40:39 +0200
Florian Tobias Schandinat [off-list ref] wrote:
Meanwhile, I'm a little unsure now...is there an action item for me
with regard to the i2c code?  I've been staring at it since your last
note, but I couldn't find any obvious problems.  I do have to say that
Harald's rework is far cleaner than what came before...
Well the main question is probably:
How does it change the behaviour towards the hardware?
I tend to think that OLPC might not be the only ones who did something 
weird with it....and we already know that we shouldn't trust the 
documentation too much.
I was able to narrow this issue down to the fourth bus. So with
if (i = 4)
	continue;
in the bus creation loop I'm able to get a working framebuffer which 
does not have the issues mentioned. Any ideas what should be done now?


Thanks,

Florian Tobias Schandinat
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help