Hi
Just a follow-up on the SYNCLOST problem we are seeing with the
framebuffer driver.
It seems as if we only get SYNCLOST signal in the display controller
interrupt handler when we activate the ADS7846 touchscreen which is
connected via SPI. Maybe signal integrity is to blame, since both LCD
Immediate followup:
I got the touchscreen working together with framebuffer by setting the
SPI clock to 50 kHz instead of 1.5 MHz in
arch/arm/mach-omap2/board-2430sdp.c.
BR
Simon Braunschmidt
2008/5/5 Simon Braunschmidt [EMAIL PROTECTED]:
Hi
Just a follow-up on the SYNCLOST problem we are
It's wrapped and you need to add some spaces before %s in all of them
:-p
In any case, this is only for testing purpose, i think it shouldn't be
applied. I don't have lcd working on 3430sdp as well but never look at
it.
Ya i have seen its wrapped, stupid google webmailer wrapping my
Hi Arun, all
I just switched to 2.6.23-omap1, which is booting with framebuffer.
Which recent kernel version would you recommend to get down and dirty
with Android on the 2430sdp?
btw 2.6.24-omap1 is booting for me on 2430sdp, but with not
framebuffer, though framebuffer gets registered
On Thu, Apr 24, 2008 at 06:57:48PM +0200, Simon Braunschmidt wrote:
Hi all
We are running 2.6.24-omap1.
We have problems to get the framebuffer driver running on a
SDP2430-VG5.0.1 board. At the moment the LCD stays dark, no penguin to
be seen, test program not displaying anything,
