and touchscreen signal go over the same flat cable.
Problem is seen on 2.6.23-omap1 with CONFIG_SPI_OMAP24XX,
CONFIG_TOUCHSCREEN_ADS7846 and CONFIG_FB_OMAP enabled, configured for
2430sdp.
Can anyone comment on this issue?
BR
Simon Braunschmidt
2008/4/25 Simon Braunschmidt [EMAIL PROTECTED]:
Hi
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
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
sources got tainted by our half-baked patching approaches, so sorry
for the noise...
Greetings, Gruessla
Simon
2008/4/25, arun c [EMAIL PROTECTED]:
On Fri, Apr 25, 2008 at 12:35 PM, Simon Braunschmidt
[EMAIL PROTECTED] wrote:
It's wrapped and you need to add some spaces before %s
, maybe montavista or something TI developed internally,
is running succesfully with framebuffer.
Help, a working .config, some insight would be much appreciated...
Regards, Gruessla
Simon Braunschmidt
The errors start right after powermanagment init according to bootlog,
maybe related?
Below
it?
I just stumbled over these kernels, does anyone know who provided them
initially and why/how they differ in this aspect and maybe others from
mvista git?
BR
Simon Braunschmidt
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to [EMAIL PROTECTED]
More
