77e196752b
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)> |
||
|---|---|---|
| .. | ||
| cyblafb | ||
| 00-INDEX | ||
| arkfb.txt | ||
| aty128fb.txt | ||
| cirrusfb.txt | ||
| cmap_xfbdev.txt | ||
| deferred_io.txt | ||
| fbcon.txt | ||
| framebuffer.txt | ||
| gxfb.txt | ||
| imacfb.txt | ||
| intel810.txt | ||
| intelfb.txt | ||
| internals.txt | ||
| lxfb.txt | ||
| matroxfb.txt | ||
| metronomefb.txt | ||
| modedb.txt | ||
| pvr2fb.txt | ||
| pxafb.txt | ||
| s3fb.txt | ||
| sa1100fb.txt | ||
| sh7760fb.txt | ||
| sisfb.txt | ||
| sstfb.txt | ||
| tgafb.txt | ||
| tridentfb.txt | ||
| uvesafb.txt | ||
| vesafb.txt | ||
| viafb.modes | ||
| viafb.txt | ||
| vt8623fb.txt | ||