| Age | Commit message (Collapse) | Author |
|---|
|
cpp file
The destructor doesn't need to be a pure-virtual function.
|
|
"Better Hid" Rework Part 1
|
|
shader_decompiler: Fix TLDS
|
|
Implement flushing in the rasterizer cache
|
|
svc: Clarify enum values for AddressSpaceBaseAddr and AddressSpaceSize in svcGetInfo()
|
|
Implement Arrays on Tex Instruction
|
|
savedata_factory: Add DeviceSaveData and fix TemporaryStorage
|
|
|
|
|
|
Reason for the change is to allow both docked and undocked mode to work
|
|
|
|
- This will be used as a catch-all for slow-but-accurate GPU emulation paths.
|
|
|
|
|
|
|
|
|
|
- This does not really have anything to do with OpenGL.
|
|
|
|
|
|
- These cannot be used within the cache, as they change cache state.
|
|
|
|
|
|
|
|
guest RAM.
|
|
content_archive/patch_manager: Lower log levels to eliminate some unnecessary logs
|
|
* Implement VI ConvertScalingMode
* Fixed push enum
* Scale mode now uses Nintendo scale mode as an enum as well
|
|
core: Convert shared_ptr instances into unique_ptr instances where applicable for System and Cpu
|
|
Required for TemporaryStorage saves (in addition to SaveDataType)
|
|
Uses the same path as SaveData except with UID 0. Adds a warning if UID is not 0.
|
|
shared_ptrs where applicable
The data retrieved in these cases are ultimately chiefly owned by either
the RegisteredCache instance itself, or the filesystem factories. Both
these should live throughout the use of their contained data. If they
don't, it should be considered an interface/design issue, and using
shared_ptr instances here would mask that, as the data would always be
prolonged after the main owner's lifetime ended.
This makes the lifetime of the data explicit and makes it harder to
accidentally create cyclic references. It also makes the interface
slightly more flexible than the previous API, as a shared_ptr can be
created from a unique_ptr, but not the other way around, so this allows
for that use-case if it ever becomes necessary in some form.
|
|
web_service: Make linkage of web_service-related externals and the library private
|
|
yuzu/main: Apply the [[maybe_unused]] attribute to the parameter of SetDiscordEnabled
|
|
These are just the size of the data being passed in, so we can specify
that via the size() member function.
|
|
aoc: Fix various bugs in current AOC implementation
|
|
nro/nso: Minor error handling changes
|
|
crypto: Various crypto fixes for quickstart guide
|
|
If a malformed NSO is attempted to be loaded, we shouldn't continue
onwards. We should be reporting an error and bailing out.
|
|
Control Code 0xf means to unconditionally execute the instruction. This
value is passed to most BRA, EXIT and SYNC instructions (among others)
but this may not always be the case.
|
|
|
|
|
|
|
|
There's no need for shared ownership here, as the only owning class
instance of those Cpu instances is the System class itself. We can also
make the thread_to_cpu map use regular pointers instead of shared_ptrs,
given that the Cpu instances will always outlive the cases where they're
used with that map.
|
|
Like the barrier, this is owned entirely by the System and will always
outlive the encompassing state, so shared ownership semantics aren't
necessary here.
|
|
This will always outlive the Cpu instances, since it's destroyed after
we destroy the Cpu instances on shutdown, so there's no need for shared
ownership semantics here.
|
|
|
|
|
|
This function doesn't need to care about ownership semantics, so we can
just pass it a reference to the file itself, rather than a
std::shared_ptr alias.
|
|
svcGetInfo()
So, one thing that's puzzled me is why the kernel seemed to *not* use
the direct code address ranges in some cases for some service functions.
For example, in svcMapMemory, the full address space width is compared
against for validity, but for svcMapSharedMemory, it compares against
0xFFE00000, 0xFF8000000, and 0x7FF8000000 as upper bounds, and uses
either 0x200000 or 0x8000000 as the lower-bounds as the beginning of the
compared range. Coincidentally, these exact same values are also used in
svcGetInfo, and also when initializing the user address space, so this
is actually retrieving the ASLR extents, not the extents of the address
space in general.
|
|
Falls back to title ID + 0x1000, which is what HOS does.
|
|
key_manager/partition_data_manager: Minor changes
|
