8 commits

Author	SHA1	Message	Date
Subv	81bcb331f8	NV: Move the nv device nodes to their own directory and namespace.	2018-01-10 23:28:40 -05:00
Subv	8c39b10e47	VI: Use a Pulse event instead of OneShot for the vblank events. ... This prevents missing frames if the vblank fires between the DequeueBuffer and Wait(vsync) calls	2018-01-10 23:28:36 -05:00
Subv	2d5bf5a379	NV: Expose the nvdisp_disp0 device and a weak reference to the nvdrv:a service. ... NVFlinger will call into the nvdisp_disp0 device to perform screen flips, bypassing the ioctl interface. We now have the address of the framebuffer to draw, we just need to actually put it on the screen.	2018-01-10 23:28:29 -05:00
Subv	91a0d29466	NV: Determine what buffer to draw for each layer of each display. ... Don't try to draw buffers that the guest application is using, only queued buffers are eligible for drawing. Drawing actual pixels is still not implemented.	2018-01-10 23:28:25 -05:00
Subv	1b907ea655	NV: Signal all display's vsync event 60 times per second.	2018-01-10 23:28:22 -05:00
Subv	67222ea3a6	NV: Give each display its own vsync event.	2018-01-10 23:28:19 -05:00
Subv	a7c31ad468	NV: Keep track of Displays, Layers and BufferQueues in nvflinger.	2018-01-10 23:28:16 -05:00
Subv	2d06628c52	NV: Implemented (with stubs) the vi:m service and some of its subservices. ... The homebrew display test application now properly writes graphics data to the graphics buffer but we still don't have a way to compose the display layers.	2018-01-10 23:28:09 -05:00