- 03 Jan, 2019 7 commits
-
-
bunnei authored
service/vi: Implement OpenDefaultDisplay in terms of OpenDisplay
-
bunnei authored
service/vi: Implement SetDisplayEnabled()
-
bunnei authored
qt: Add setting to prompt for user on game boot
-
bunnei authored
qt: Use ProfileSelectionDialog when selecting user for save data
-
Lioncash authored
This IPC command is simply a stub inside the actual service itself, and just returns a successful error code regardless of input. This is likely only retained in the service interface to not break older code that relied upon it succeeding in some way.
-
bunnei authored
service/vi: Log more information where applicable
-
Lioncash authored
In many cases, we didn't bother to log out any of the popped data members. This logs them out to the console within the logging call to provide more contextual information.
-
- 02 Jan, 2019 5 commits
-
-
Lioncash authored
Internally within the vi services, this is essentially all that OpenDefaultDisplay does, so it's trivial to just do the same, and forward the default display string into the function.
-
bunnei authored
gl_rasterizer_cache: Texture view if shader samples array but OGL is not
-
bunnei authored
Port citra-emu/citra#4187: "Qt/Configure: Use sidebar to divide tabs into smaller groups"
-
bunnei authored
yuzu: Fix truncation warnings within UI code
-
bunnei authored
core/kernel: Remove unnecessary inclusions
-
- 01 Jan, 2019 3 commits
- 31 Dec, 2018 12 commits
-
-
bunnei authored
arm_interface: Minor cleanup
-
bunnei authored
kernel/svc: Sanitize core and priority masks within CreateThread
-
bunnei authored
externals: Update fmt to 5.3.0
-
Lioncash authored
This is a bounds check to ensure that the thread priority is within the valid range of 0-64. If it exceeds 64, that doesn't necessarily mean that an actual priority of 64 was expected (it actually means whoever called the function screwed up their math). Instead clarify the message to indicate the allowed range of thread priorities.
-
Lioncash authored
Now that we handle the kernel capability descriptors we can correct CreateThread to properly check against the core and priority masks like the actual kernel does.
-
Lioncash authored
Makes them consistent with their kernel capability counterparts.
-
Lioncash authored
Rather than use a switch here, this can be collapsed into a simple range check, which is a little easier on the eyes.
-
Lioncash authored
Makes it consistent with the rest of the includes.
-
Lioncash authored
This function doesn't modify instance state, so it can be made const.
-
Lioncash authored
Two of these variables have fixed values, so we can make that immediately obvious from the get-go.
-
Lioncash authored
Namespaces don't require the use of a semicolon. Silences a -Wextra-semi warning.
-
Sebastian Valle authored
kernel/process: Start the main thread using the specified ideal core
-
- 30 Dec, 2018 5 commits
-
-
bunnei authored
Print backtrace on svcBreak
-
bunnei authored
service/time: Minor cleanup
-
ReinUsesLisp authored
When a shader samples a texture array but that texture in OpenGL is created without layers, use a texture view to increase the texture hierarchy. For example, instead of binding a GL_TEXTURE_2D bind a GL_TEXTURE_2D_ARRAY view.
-
Lioncash authored
Moves some variables closer to their actual usage sites.
-
Lioncash authored
Updates fmt from 5.2.1 to 5.3.0
-
- 29 Dec, 2018 3 commits
-
-
Lioncash authored
-
David Marcec authored
-
bunnei authored
gpu: Remove PixelFormat G8R8U and G8R8S, as they do not seem to exist.
-
- 28 Dec, 2018 5 commits
-
-
bunnei authored
- Fixes UI rendering issues in The Legend of Zelda: Breath of the Wild.
-
bunnei authored
audio_core: Convert LOG_CRITICAL + UNREACHABLE over to UNIMPLEMENTED/UNIMPLEMENTED_MSG
-
Lioncash authored
These two macros being used in tandem were used prior to the introduction of UNIMPLEMENTED and UNIMPLEMENTED_MSG. This provides equivalent behavior, just with less typing/reading involved.
-
Lioncash authored
This matches kernel behavior in that processes are started using their specified ideal core, rather than always starting on core 0.
-
Lioncash authored
This makes the naming more closely match its meaning. It's just a preferred core, not a required default core. This also makes the usages of this term consistent across the thread and process implementations.
-