summaryrefslogtreecommitdiffstats
path: root/src/core/hle/service/vi/display (follow)
Commit message (Collapse)AuthorAgeFilesLines
* core: Make variable shadowing a compile-time errorLioncash2021-05-162-6/+6
| | | | | | Now that we have most of core free of shadowing, we can enable the warning as an error to catch anything that may be remaining and also eliminate this class of logic bug entirely.
* common: Rename NON_COPYABLE/NON_MOVABLE with YUZU_ prefix.bunnei2021-05-061-2/+2
|
* hle: kernel: Migrate KReadableEvent and KWritableEvent to KAutoObject.bunnei2021-05-062-3/+3
|
* hle: kernel: Ensure all kernel objects with KAutoObject are properly created.bunnei2021-05-061-0/+1
|
* hle: kernel: Migrate KEvent to KAutoObject.bunnei2021-05-062-13/+10
|
* hle: kernel: Refactor IPC interfaces to not use std::shared_ptr.bunnei2021-05-061-1/+1
|
* service: Eliminate cases of member shadowingLioncash2021-04-262-21/+20
| | | | | Resolves a few localized instances of member variable shadowing. Brings us a little closer to turning shadowing warnings into errors.
* hle: kernel: Reimplement KReadableEvent and KWritableEvent.bunnei2021-02-052-6/+11
|
* hle: kernel: Rename WritableEvent to KWritableEvent.bunnei2021-02-052-2/+2
|
* hle: kernel: Rename ReadableEvent to KReadableEvent.bunnei2021-02-052-3/+3
|
* service: vi: Implement CloseLayer.bunnei2020-01-042-10/+26
| | | | - Needed for Undertale.
* kernel: Replace usage of boost::intrusive_ptr with std::shared_ptr for kernel objects. (#3154)bunnei2019-11-252-2/+2
| | | | | | * kernel: Replace usage of boost::intrusive_ptr with std::shared_ptr for kernel objects. - See https://github.com/citra-emu/citra/pull/4710 for details.
* kernel: events: Remove ResetType::Automatic.bunnei2019-11-031-2/+2
| | | | | | | | - 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
* Deglobalize System: ViDavid Marcec2019-09-222-3/+3
|
* core/kernel/object: Rename ResetType enum membersLioncash2019-05-181-1/+1
| | | | | | | | | | | | | 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.
* service/nvflinger: Store BufferQueue instances as regular data membersLioncash2019-02-222-3/+3
| | | | | | | The NVFlinger service is already passed into services that need to guarantee its lifetime, so the BufferQueue instances will already live as long as they're needed. Making them std::shared_ptr instances in this case is unnecessary.
* service/vi/vi_layer: Convert Layer struct into a classLioncash2019-02-212-3/+3
| | | | | | | Like the previous changes made to the Display struct, this prepares the Layer struct for changes to its interface. Given Layer will be given more invariants in the future, we convert it into a class to better signify that.
* service/nvflinger: Move display specifics over to vi_displayLioncash2019-02-212-1/+120
| | | | | | | | | With the display and layer structures relocated to the vi service, we can begin giving these a proper interface before beginning to properly support the display types. This converts the display struct into a class and provides it with the necessary functions to preserve behavior within the NVFlinger class.
* service/nvflinger: Relocate definitions of Layer and Display to the vi serviceLioncash2019-02-202-0/+50
These are more closely related to the vi service as opposed to the intermediary nvflinger. This also places them in their relevant subfolder, as future changes to these will likely result in subclassing to represent various displays and services, as they're done within the service itself on hardware. The reasoning for prefixing the display and layer source files is to avoid potential clashing if two files with the same name are compiled (e.g. if 'display.cpp/.h' or 'layer.cpp/.h' is added to another service at any point), which MSVC will actually warn against. This prevents that case from occurring. This also presently coverts the std::array introduced within f45c25aabacc70861723a7ca1096a677bd987487 back to a std::vector to allow the forward declaration of the Display type. Forward declaring a type within a std::vector is allowed since the introduction of N4510 (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4510.html) by Zhihao Yuan.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-14 10:02:11 +0200