diff options
| author | Antonino A. Daplas <adaplas@gmail.com> | 2007-05-08 09:38:57 +0200 |
|---|---|---|
| committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-05-08 20:15:30 +0200 |
| commit | 68648ed1f58d98b8e8d994022e5e25331fbfe42a (patch) | |
| tree | 77c721d08b11aba58a30779e7b3294a96dd7fb29 /drivers/video/arcfb.c | |
| parent | skeletonfb: documentation error fixes (diff) | |
| download | linux-68648ed1f58d98b8e8d994022e5e25331fbfe42a.tar.xz linux-68648ed1f58d98b8e8d994022e5e25331fbfe42a.zip | |
fbdev: add drawing functions for framebuffers in system RAM
The generic drawing functions (cfbimgblt, cfbcopyarea, cfbfillrect) assume
that the framebuffer is in IO memory. However, we have 3 drivers (hecubafb,
arcfb, and vfb) where the framebuffer is allocated from system RAM (via
vmalloc). Using _raw_read/write and family for these drivers (as used in
the cfb* functions) is illegal, especially in other platforms.
Create 3 new drawing functions, based almost entirely from the original
except that the framebuffer memory is assumed to be in system RAM.
These are named as sysimgblt, syscopyarea, and sysfillrect.
Signed-off-by: Antonino Daplas <adaplas@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/video/arcfb.c')
0 files changed, 0 insertions, 0 deletions