On ARM if memattr is not overriden mmap(2) maps framebuffer memory as WBWA which means part of changes to content in userland end up in cache and appear on screen gradually as cache lines are evicted. This change adds configurable memattr that hardware fb implementation can set to get the memory mapping type it requires: - Add new flag FB_FLAG_MEMATTR that indicates that framebuffer driver overrides default memattr - Add new field fb_memattr to struct fb_info to specify requested memattr Reviewed by: ray Differential Revision: https://reviews.freebsd.org/D8064 |
||
---|---|---|
.. | ||
boot_font.c | ||
creator_vt.c | ||
creator.c | ||
creatorreg.h | ||
fb_if.m | ||
fb.c | ||
fbd.c | ||
fbreg.h | ||
gallant12x22.c | ||
gfb.h | ||
machfb.c | ||
machfbreg.h | ||
s3_pci.c | ||
splash_bmp.c | ||
splash_pcx.c | ||
splash_txt.c | ||
splash.c | ||
splashreg.h | ||
vesa.c | ||
vesa.h | ||
vga.c | ||
vgareg.h |