0df1b1c36f
If we clear the framebuffer and then flush it back to memory using cache operations, the writes are going to be full cachelines at a time. If we make it uncacheable first, the writes will be serialized writes of whatever sized chunks memset uses, probably 4 bytes or less. BUG=None TEST=Built and booted on Snow. Verified that graphics were drawn completely. BRANCH=None Change-Id: I94c81145b422eb440c7698273e7f3944c5ee486e Signed-off-by: Gabe Black <gabeblack@google.com> Reviewed-on: https://gerrit.chromium.org/gerrit/55640 Commit-Queue: Stefan Reinauer <reinauer@google.com> Reviewed-by: Stefan Reinauer <reinauer@google.com> Tested-by: Stefan Reinauer <reinauer@google.com> |
||
|---|---|---|
| .. | ||
| amd | ||
| armltd | ||
| intel | ||
| samsung | ||
| via | ||
| x86 | ||
| Kconfig | ||
| Makefile.inc | ||