| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| | |
service: HLE multiprocess
|
| | |
| |
| |
| | |
Converts services to have their own processes
|
| |/ |
|
| | |
|
| |
|
|
|
| |
This formats all copyright comments according to SPDX formatting guidelines.
Additionally, this resolves the remaining GPLv2 only licensed files by relicensing them to GPLv2.0-or-later.
|
| |\
| |
| | |
general: Get the current process program id directly from the system
|
| | |
| |
| |
| | |
This allows us to avoid including KProcess' header file in files that only need to get the current process' program id.
|
| | | |
|
| |\ \
| |/
|/| |
service: aoc: Stub more 13.x functions used by Animal Crossing
|
| | |
| |
| |
| | |
Used by Animal Crossing: New Horizons v2.0.0 DLC
|
| | |
| |
| |
| | |
Used by Animal Crossing: New Horizons v2.0.0 DLC
|
| |/ |
|
| |
|
|
| |
The service context helps to manage all created events and allows us to close them upon destruction.
|
| |
|
|
| |
- This is used by the latest update of Doom Eternal.
|
| |
|
|
| |
Transition to PascalCase for result names.
|
| |
|
|
| |
Transition to PascalCase for result names.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
- Removes a dependency on core and input_common from common.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
fsp_srv: Implement OpenDataStorageWithProgramIndex
|
| | | |
|
| | |
| |
| |
| |
| | |
- Used by Pokémon Café Mix
- Used by DOOM: Eternal
|
| | |
| |
| |
| |
| | |
- Used by Pokémon Café Mix
- Used by DOOM: Eternal
|
| |/
|
|
|
| |
- Used by Pokémon Café Mix
- Used by DOOM: Eternal
|
| |
|
|
|
| |
Completely removes all usages of the global system instance within the
services code by passing in the using system instance to the services.
|
| |
|
|
|
|
|
| |
With this, only 19 usages of the global system instance remain within
the core library.
We're almost there.
|
| |
|
|
|
|
|
|
|
| |
Resolves numerous deprecation warnings throughout the codebase due to
inclusion of this header. Now building core should be significantly less
noisy (and also relying on less global state).
This also uncovered quite a few modules that were relying on indirect
includes, which have also been fixed.
|
| |
|
|
|
| |
* aoc: Update function table
* Remove comments
|
| |\
| |
| | |
service: Update function tables
|
| | |
| |
| |
| |
| |
| | |
Keeps the function tables up to date.
Updated based off information from Switchbrew.
|
| |/
|
|
|
| |
These are fairly trivial to resolve and most of the changes entail
using RESULT_UNKNOWN over ResultCode(-1).
|
| |
|
|
|
|
|
|
| |
- This does not actually seem to exist in the real kernel - games reset these automatically.
# Conflicts:
# src/core/hle/service/am/applets/applets.cpp
# src/core/hle/service/filesystem/fsp_srv.cpp
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Previously, the code was accumulating data into a std::vector and then
tossing all of it away if a setting was disabled.
Instead, we can just check if it's disabled and do no work at all if
possible. If it's enabled, then we can append to the vector and
allocate.
Unlikely to impact usage much, but it is slightly less sloppy with
resources.
|
| |
|
|
|
| |
Removes two header dependencies related to file handling that aren't
actually used within the source file.
|
| |
|
|
|
|
| |
A few of the aoc service stubs/implementations weren't fully popping all
of the parameters passed to them. This ensures that all parameters are
popped and, at minimum, logged out.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Renames the members to more accurately indicate what they signify.
"OneShot" and "Sticky" are kind of ambiguous identifiers for the reset
types, and can be kind of misleading. Automatic and Manual communicate
the kind of reset type in a clearer manner. Either the event is
automatically reset, or it isn't and must be manually cleared.
The "OneShot" and "Sticky" terminology is just a hold-over from Citra
where the kernel had a third type of event reset type known as "Pulse".
Given the Switch kernel only has two forms of event reset types, we
don't need to keep the old terminology around anymore.
|
| |
|
|
| |
Updates function tables based off information from SwitchBrew.
|
| | |
|
| | |
|
| |\
| |
| | |
filesystem: De-globalize registered_cache_union
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
We can just return a new instance of this when it's requested. This only
ever holds pointers to the existing registed caches, so it's not a large
object. Plus, this also gets rid of the need to keep around a separate
member function just to properly clear out the union.
Gets rid of one of five globals in the filesystem code.
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
| |
We can just call the function instead of duplicating the code here. This
also prevents an unused function warning.
We also don't need to take the lambda capture by reference. It's just a
u64 value, so by value is fine here.
|
| |
|
|
| |
This event signals the game when new DLC is purchased from the eShop while the game is running. Since, for the forseeable future, yuzu will not have this ability, it seems safe to stub with a dummy event that will never fire. This is needed to boot Sonic Mania Plus (update v1.04).
|
| |
|
| |
Falls back to title ID + 0x1000, which is what HOS does.
|
| | |
|
| |
|
|
|
|
| |
Word count should be 3 since we're pushing a result code and a u32.
Also fixed up compiler warnings due to casting
|
| |
|
|
| |
In some games (Splatoon 2 and Splatoon 2 Splatfest World Premiere, notably), pass offset=0 and count=2047 into the ListAddOnContent method which should return all DLCs for the current title. The (presumably) intended behavior is to successfully return a empty array but because of a < v. <= in an if statement, a failure error code was returned causing these games to svcBreak. This fixes that if statement.
|
| | |
|
| |
|
| |
Command #5
|
| |
|
|
| |
Commands #2, #3, and #7
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a destructor isn't defaulted into a cpp file, it can cause the use
of forward declarations to seemingly fail to compile for non-obvious
reasons. It also allows inlining of the construction/destruction logic
all over the place where a constructor or destructor is invoked, which
can lead to code bloat. This isn't so much a worry here, given the
services won't be created and destroyed frequently.
The cause of the above mentioned non-obvious errors can be demonstrated
as follows:
------- Demonstrative example, if you know how the described error happens, skip forwards -------
Assume we have the following in the header, which we'll call "thing.h":
\#include <memory>
// Forward declaration. For example purposes, assume the definition
// of Object is in some header named "object.h"
class Object;
class Thing {
public:
// assume no constructors or destructors are specified here,
// or the constructors/destructors are defined as:
//
// Thing() = default;
// ~Thing() = default;
//
// ... Some interface member functions would be defined here
private:
std::shared_ptr<Object> obj;
};
If this header is included in a cpp file, (which we'll call "main.cpp"),
this will result in a compilation error, because even though no
destructor is specified, the destructor will still need to be generated by
the compiler because std::shared_ptr's destructor is *not* trivial (in
other words, it does something other than nothing), as std::shared_ptr's
destructor needs to do two things:
1. Decrement the shared reference count of the object being pointed to,
and if the reference count decrements to zero,
2. Free the Object instance's memory (aka deallocate the memory it's
pointing to).
And so the compiler generates the code for the destructor doing this inside main.cpp.
Now, keep in mind, the Object forward declaration is not a complete type. All it
does is tell the compiler "a type named Object exists" and allows us to
use the name in certain situations to avoid a header dependency. So the
compiler needs to generate destruction code for Object, but the compiler
doesn't know *how* to destruct it. A forward declaration doesn't tell
the compiler anything about Object's constructor or destructor. So, the
compiler will issue an error in this case because it's undefined
behavior to try and deallocate (or construct) an incomplete type and
std::shared_ptr and std::unique_ptr make sure this isn't the case
internally.
Now, if we had defaulted the destructor in "thing.cpp", where we also
include "object.h", this would never be an issue, as the destructor
would only have its code generated in one place, and it would be in a
place where the full class definition of Object would be visible to the
compiler.
---------------------- End example ----------------------------
Given these service classes are more than certainly going to change in
the future, this defaults the constructors and destructors into the
relevant cpp files to make the construction and destruction of all of
the services consistent and unlikely to run into cases where forward
declarations are indirectly causing compilation errors. It also has the
plus of avoiding the need to rebuild several services if destruction
logic changes, since it would only be necessary to recompile the single
cpp file.
|
| | |
|
| | |
|
| |
|
|
| |
Tidies up namespace declarations
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
