diff options
| author | Antonino A. Daplas <[email protected]> | 2007-05-08 00:38:57 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2007-05-08 11:15:30 -0700 |
| commit | 68648ed1f58d98b8e8d994022e5e25331fbfe42a (patch) | |
| tree | 77c721d08b11aba58a30779e7b3294a96dd7fb29 /scripts/patch-kernel | |
| parent | a42dc9d4804cc5e111952008492dae9d34c6a541 (diff) | |
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 <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'scripts/patch-kernel')
0 files changed, 0 insertions, 0 deletions