From a6c925112a4e97feb21a8ae577f2993d0617cb1f Mon Sep 17 00:00:00 2001
From: bunnei <ericbunnie@gmail.com>
Date: Sun, 27 Apr 2014 12:41:25 -0400
Subject: [PATCH] hackish but working way to set the framebuffer location to
VRAM (used in ARM11 demos tested thus far, e.g. yeti3DS)
---
src/core/hle/service/gsp.cpp | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/src/core/hle/service/gsp.cpp b/src/core/hle/service/gsp.cpp
index 24e9f18dc0..88c1f1a0fb 100644
--- a/src/core/hle/service/gsp.cpp
+++ b/src/core/hle/service/gsp.cpp
@@ -23,8 +23,8 @@ enum {
/// Read a GSP GPU hardware register
void ReadHWRegs(Service::Interface* self) {
- static const u32 framebuffer_1[] = {LCD::VRAM_TOP_LEFT_FRAME1, LCD::VRAM_TOP_RIGHT_FRAME1};
- static const u32 framebuffer_2[] = {LCD::VRAM_TOP_LEFT_FRAME2, LCD::VRAM_TOP_RIGHT_FRAME2};
+ static const u32 framebuffer_1[] = {LCD::PADDR_VRAM_TOP_LEFT_FRAME1, LCD::PADDR_VRAM_TOP_RIGHT_FRAME1};
+ static const u32 framebuffer_2[] = {LCD::PADDR_VRAM_TOP_LEFT_FRAME2, LCD::PADDR_VRAM_TOP_RIGHT_FRAME2};
u32* cmd_buff = (u32*)HLE::GetPointer(HLE::CMD_BUFFER_ADDR + Service::kCommandHeaderOffset);
u32 reg_addr = cmd_buff[1];
@@ -33,14 +33,20 @@ void ReadHWRegs(Service::Interface* self) {
switch (reg_addr) {
+ // NOTE: Calling SetFramebufferLocation here is a hack... Not sure the correct way yet to set
+ // whether the framebuffers should be in VRAM or GSP heap, but from what I understand, if the
+ // user application is reading from either of these registers, then its going to be in VRAM.
+
// Top framebuffer 1 addresses
case REG_FRAMEBUFFER_1:
+ LCD::SetFramebufferLocation(LCD::FRAMEBUFFER_LOCATION_VRAM);
memcpy(dst, framebuffer_1, size);
break;
// Top framebuffer 2 addresses
case REG_FRAMEBUFFER_2:
- memcpy(dst, framebuffer_1, size);
+ LCD::SetFramebufferLocation(LCD::FRAMEBUFFER_LOCATION_VRAM);
+ memcpy(dst, framebuffer_2, size);
break;
default:
--
GitLab