[Xorg-driver-geode] display mode with 800x480 on geode-2.11.1

[wan michael]

thank you for your quick repley

firstly, I have added the 800x480 mode into the Geode LX KFB , that is,
it is in lxfb_core.c, but don't verify the dot clock to the PLL frequencies
in lx_ops.c,  I also wan to know how to verify the dot clock.

secondly, the LCD display is connected via TFT. if like what you said,
it would not need any DDC.

thirdly, video playback would be available, but not to an external monitor,
these opiton can be setup through register in hardware, but now not setup,
and they would be setup in the near future, right?

fourthly, is the Geode KFB different from the xorg geode dirver code? there
are some codes to setup those option to reference in xorg geode driver.

fifithly, cfbcopyarea.ko module, and so on, is related to KFB, not drm.
if I choose Geode KFB or VESA KFB, I can also select theose modules.

another more question related to touchscreen, as it's geode-based on, it's
wm97xx-ts. I see one line of output after loading the kernel module
wm97xx-ts.ko,
the output is "NO IRQ specified", I have no idea of how to specify IRQ for
the
module, because there is nothing about IRQ when used in xorg-x11.

best regards

michael wan

2009/5/1 John Yoder <john.yoder at twny.net>

> The most basic problem I see is that there isn't a mode for your screen
> in the resolution table for the Geode LX KFB. I expect the TFT is not
> connected via VGA, so there would not be any DDC. If this is incorrect,
> let me know. All that should be required is for you put the resolution
> into lxfb_core.c. Verify that the dot clock corresponds to the PLL
> frequencies in lx_ops.c before you recompile. Recompile the kernel, and
> reboot.
>
> The performance for the LX KFB is not worse then the VESA KFB. Whether
> you require any additional performance then the VEAS KFB is unknown. I
> don't know what apps you are trying to have available. If it is Video
> Playback, then the hardware YUV -> RGB conversion will most likely be
> required. It is dependent on the resolution and codec of the clip.
> Another consideration is whether the videos will need to be scaled or
> not. for instance, playback to an external monitor. These options are
> available in hardware, but not currently available in either the LX KFB
> or VESA KFB. So this would be done in software. The code to enable these
> features are available in a couple places including the Xorg geode
> driver. Pulling code from one source and adding it to another is
> possible but can be problematic. It can be done, just a significant bit
> of work.
>
> Since I have not worked with Android I am not sure how these modules are
> related. From Chris Balls' response, they are related to the KFB not
> drm. I am not certain what the outcome would be by selecting them.
>
> Best Regards,
>
> John Yoder
>
> On Fri, 2009-05-01 at 00:46 +0800, wan michael wrote:
> > it often blinks after booting, not only at boot time. whether using
> > vesa kfb
> > would be better than geode kfb since geode lx kfb is very basic and
> > not feature rich.
> > android uses opengl-es, not xorg server. like cfbcopyarea.ko,
> > cfbfillrect.ko and so on,
> > are they related to kfb or drm? selecting these modules can improve
> > display even without
> > hardware acceleration?
> >
> >
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.x.org/archives/xorg-driver-geode/attachments/20090501/34beec24/attachment.htm