<div>thank you for your quick repley</div>
<div> </div>
<div>firstly, I have added the 800x480 mode into the Geode LX KFB , that is, </div>
<div>it is in lxfb_core.c, but don't verify the dot clock to the PLL frequencies </div>
<div>in lx_ops.c, I also wan to know how to verify the dot clock.</div>
<div> </div>
<div>secondly, the LCD display is connected via TFT. if like what you said, </div>
<div>it would not need any DDC.</div>
<div> </div>
<div>thirdly, video playback would be available, but not to an external monitor,</div>
<div>these opiton can be setup through register in hardware, but now not setup,</div>
<div>and they would be setup in the near future, right?</div>
<div> </div>
<div>fourthly, is the Geode KFB different from the xorg geode dirver code? there</div>
<div>are some codes to setup those option to reference in xorg geode driver.</div>
<div> </div>
<div>fifithly, cfbcopyarea.ko module, and so on, is related to KFB, not drm.</div>
<div>if I choose Geode KFB or VESA KFB, I can also select theose modules.</div>
<div> </div>
<div>another more question related to touchscreen, as it's geode-based on, it's </div>
<div>wm97xx-ts. I see one line of output after loading the kernel module wm97xx-ts.ko,</div>
<div>the output is "NO IRQ specified", I have no idea of how to specify IRQ for the </div>
<div>module, because there is nothing about IRQ when used in xorg-x11. </div>
<div> </div>
<div>best regards</div>
<div> </div>
<div>michael wan<br><br></div>
<div class="gmail_quote">2009/5/1 John Yoder <span dir="ltr"><<a href="mailto:john.yoder@twny.net">john.yoder@twny.net</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">The most basic problem I see is that there isn't a mode for your screen<br>in the resolution table for the Geode LX KFB. I expect the TFT is not<br>
connected via VGA, so there would not be any DDC. If this is incorrect,<br>let me know. All that should be required is for you put the resolution<br>into lxfb_core.c. Verify that the dot clock corresponds to the PLL<br>frequencies in lx_ops.c before you recompile. Recompile the kernel, and<br>
reboot.<br><br>The performance for the LX KFB is not worse then the VESA KFB. Whether<br>you require any additional performance then the VEAS KFB is unknown. I<br>don't know what apps you are trying to have available. If it is Video<br>
Playback, then the hardware YUV -> RGB conversion will most likely be<br>required. It is dependent on the resolution and codec of the clip.<br>Another consideration is whether the videos will need to be scaled or<br>not. for instance, playback to an external monitor. These options are<br>
available in hardware, but not currently available in either the LX KFB<br>or VESA KFB. So this would be done in software. The code to enable these<br>features are available in a couple places including the Xorg geode<br>
driver. Pulling code from one source and adding it to another is<br>possible but can be problematic. It can be done, just a significant bit<br>of work.<br><br>Since I have not worked with Android I am not sure how these modules are<br>
related. From Chris Balls' response, they are related to the KFB not<br>drm. I am not certain what the outcome would be by selecting them.<br><br>Best Regards,<br><font color="#888888"><br>John Yoder<br></font>
<div>
<div></div>
<div class="h5"><br>On Fri, 2009-05-01 at 00:46 +0800, wan michael wrote:<br>> it often blinks after booting, not only at boot time. whether using<br>> vesa kfb<br>> would be better than geode kfb since geode lx kfb is very basic and<br>
> not feature rich.<br>> android uses opengl-es, not xorg server. like cfbcopyarea.ko,<br>> cfbfillrect.ko and so on,<br>> are they related to kfb or drm? selecting these modules can improve<br>> display even without<br>
> hardware acceleration?<br>><br>><br><br><br><br></div></div></blockquote></div><br>