diff options
author | Eric Miao <ycmiao@ycmiao-hp520.(none)> | 2008-12-17 14:56:54 +0800 |
---|---|---|
committer | Eric Miao <eric.miao@marvell.com> | 2008-12-29 17:59:16 +0800 |
commit | 7e4b19c95c8632b543bd510ec6c710bebb53b840 (patch) | |
tree | 5c6eeaeb949a8beded5193379fb552fb15cf8fe1 /README | |
parent | 77e196752bdd76a0c58ab082658d28c6a90fa40e (diff) | |
download | kernel_samsung_smdk4412-7e4b19c95c8632b543bd510ec6c710bebb53b840.zip kernel_samsung_smdk4412-7e4b19c95c8632b543bd510ec6c710bebb53b840.tar.gz kernel_samsung_smdk4412-7e4b19c95c8632b543bd510ec6c710bebb53b840.tar.bz2 |
[ARM] pxafb: allow pxafb_set_par() to start from arbitrary yoffset
Note the var->yres_virtual is only re-calculated from the fix.smem_len
when text mode acceleration is enabled (which is default), this is due
to the issue as Russell suggested below:
Previous experience of doing this with the X server and acornfb is that
it causes all sorts of problems - it seems to force the X server into
assuming that the framebuffer should be panned no matter what settings
you ask it for.
The recommended workaround (implemented in acornfb) is to only do these
kinds of adjustments if text mode acceleration is enabled. IIRC, the X
server should be disabling text mode acceleration when it maps the
framebuffer. I seem to remember that there are X servers which forget
to do that though.
Signed-off-by: Eric Miao <eric.miao@marvell.com>
Signed-off-by: Eric Miao <ycmiao@ycmiao-hp520.(none)>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions