diff options
author | Eric Miao <eric.miao@marvell.com> | 2008-12-15 22:54:34 -0500 |
---|---|---|
committer | Eric Miao <eric.miao@marvell.com> | 2008-12-29 04:59:16 -0500 |
commit | 77e196752bdd76a0c58ab082658d28c6a90fa40e (patch) | |
tree | 935fbe8b897d8770fff05254c6c91dc0a8058984 /Documentation/fb/vt8623fb.txt | |
parent | 5bfb4093be6ac7b6c06c8e6461d85241654acc61 (diff) |
[ARM] pxafb: allow video memory size to be configurable
The amount of video memory size is decided according to the following
order:
1. <xres> x <yres> x <bits_per_pixel> by default, which is the backward
compatible way
2. size specified in platform data
3. size specified in module parameter 'options' string or specified in
kernel boot command line (see updated Documentation/fb/pxafb.txt)
And now since the memory is allocated from system memory, the pxafb_mmap
can be removed and the default fb_mmap() should be working all right.
Also, since we now have introduced the 'struct pxafb_dma_buff' for DMA
descriptors and palettes, the allocation can be separated cleanly.
NOTE: the LCD DMA actually supports chained transfer (i.e. page-based
transfers), to simplify the logic and keep the performance (with less
TLB misses when accessing from memory mapped user space), the memory
is allocated by alloc_pages_*() to ensures it's physical contiguous.
Signed-off-by: Eric Miao <eric.miao@marvell.com>
Signed-off-by: Eric Miao <ycmiao@ycmiao-hp520.(none)>
Diffstat (limited to 'Documentation/fb/vt8623fb.txt')
0 files changed, 0 insertions, 0 deletions