Maybe Tony can work his magic with the LCM manufacturer. ;-)<br><br>-Kyle<br><br><br><div class="gmail_quote">On Sat, Mar 8, 2008 at 8:25 AM, Andy Green <<a href="mailto:andy@openmoko.com">andy@openmoko.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div><div class="Ih2E3d">Somebody in the thread at some point said:<br>
<br>
> We need a bit more information about the internal structure of the LCM.<br>
<br>
</div>If anyone is interested to get a little more data about the LCM free of<br>
NDA, Google tells us you can find a large chunk of what we are working<br>
from here (shown with wget due to embedded spaces in URL):<br>
<br>
wget -O /tmp/lcm.pdf<br>
"<a href="http://www.beck-oled-lcd-tft-display.de/display-datenblatt/typ/tpo/TD028TTEC1" target="_blank">http://www.beck-oled-lcd-tft-display.de/display-datenblatt/typ/tpo/TD028TTEC1</a><br>
Product Spec Ver1.2 .pdf"<br>
<div class="Ih2E3d"><br>
- -Andy<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.7 (GNU/Linux)<br>
Comment: Using GnuPG with Fedora - <a href="http://enigmail.mozdev.org" target="_blank">http://enigmail.mozdev.org</a><br>
<br>
</div>iD8DBQFH0pO/OjLpvpq7dMoRAk+QAKCR2UB2P1PkLMlqpyjyhrzl23xMQQCdFjHP<br>
Ps5PoLYevh1QBt6MNxsP5iE=<br>
=B4tY<br>
-----END PGP SIGNATURE-----<br>
<br>
</blockquote></div><br>