LCM flicker
joerg
joerg.twinklephone at gmx.de
Sun Mar 9 21:53:24 CET 2008
Am So 9. März 2008 schrieb Wolfgang Spraul:
> Yes, raster also found that.
> So if GTA01 does not show the problem, it's either glamo or wiring?
> Probably not the LCM.
> Allen Chang will do more investigations tomorrow.
> Werner (or raster), if you can e-mail some specific things you would
> want Allen to look at that would help...
> Wolfgang
Forwarded message:
----------------------------------
Am Sa 8. März 2008 schrieben Sie, Andy Green:
> I also remember they drive them with funny waveforms and take care to
> have no DC across the liquid crystal stuff, I have no idea how it
> applies to this.
> > with "AC" derived from some internal oscillator
> >> Additionally there is an "internal oscillator" mentioned in the docs but
> >> not defined anywhere as to what it does.
Strange beatoff freq of data refresh and cell AC oscillator??? Worth tuning
settings of all these LCM-ASIC-timers a *little* and to look for changed freq
of flicker.
>
> I took an LCM to pieces and there is one chip in the whole thing.
We both know this means nothing nowadays ;-)
When i heard of red-only flicker (i own no NEO at all, so i'm sad i can't
reproduce), i had another look to the c-ds, and i see (p.7) the Red4 and Red5
data lines to be rerouted, by a strange redesign for GTA02 (probably to save
an R-Array chip), through U6002 (LPF?!?), whereas same datalines go to
R-array(! NO LPF) RP6005 in GTA01. Well i'm wondering...
Anyway i agree, it's best to "fix" the glamo, better than to hack the LCM
cheers
jOERG
More information about the openmoko-kernel
mailing list