Lioncash 8d5d369b54 service/nvflinger: Relocate definitions of Layer and Display to the vi service ... 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 f45c25aaba 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.		2019-02-19 18:27:16 -05:00
..
buffer_queue.cpp	kernel/event: Reference ReadableEvent from WritableEvent	2018-11-29 08:48:40 -05:00
buffer_queue.h	core_timing: Rename CoreTiming namespace to Core::Timing	2019-02-12 12:42:17 -05:00
nvflinger.cpp	service/nvflinger: Relocate definitions of Layer and Display to the vi service	2019-02-19 18:27:16 -05:00
nvflinger.h	service/nvflinger: Relocate definitions of Layer and Display to the vi service	2019-02-19 18:27:16 -05:00