Lioncash 92ea1c32d6 service/vi: Unstub GetDisplayService ... This function is also supposed to check its given policy type with the permission of the service itself. This implements the necessary machinery to unstub these functions. Policy::User seems to just be basic access (which is probably why vi:u is restricted to that policy), while the other policy seems to be for extended abilities regarding which displays can be managed and queried, so this is assumed to be for a background compositor (which I've named, appropriately, Policy::Compositor).		2019-02-26 20:16:23 -05:00
..
display	service/nvflinger: Store BufferQueue instances as regular data members	2019-02-21 22:09:46 -05:00
layer	service/nvflinger: Store BufferQueue instances as regular data members	2019-02-21 22:09:46 -05:00
vi_m.cpp	service/vi: Unstub GetDisplayService	2019-02-26 20:16:23 -05:00
vi_m.h	service/vi: Remove use of a module class	2019-02-26 17:44:03 -05:00
vi_s.cpp	service/vi: Unstub GetDisplayService	2019-02-26 20:16:23 -05:00
vi_s.h	service/vi: Remove use of a module class	2019-02-26 17:44:03 -05:00
vi_u.cpp	service/vi: Unstub GetDisplayService	2019-02-26 20:16:23 -05:00
vi_u.h	service/vi: Remove use of a module class	2019-02-26 17:44:03 -05:00
vi.cpp	service/vi: Unstub GetDisplayService	2019-02-26 20:16:23 -05:00
vi.h	service/vi: Unstub GetDisplayService	2019-02-26 20:16:23 -05:00