On 02/01/2017 15:32, Thierry Reding wrote:
On Tue, Dec 27, 2016 at 01:57:21PM +0100, Axel Davy wrote:
Hi Thierry,
Could you explain why in this situation default_fd would be a non-renderable
device node ?
This is preparatory work to allow drivers for split display/render
setups to be tied toge
On Tue, Dec 27, 2016 at 01:57:21PM +0100, Axel Davy wrote:
> Hi Thierry,
>
> Could you explain why in this situation default_fd would be a non-renderable
> device node ?
This is preparatory work to allow drivers for split display/render
setups to be tied together within Mesa. If you want accelera
Hi Thierry,
Could you explain why in this situation default_fd would be a
non-renderable device node ?
In my understanding, for X11 DRI3 the Xserver is supposed to give you a
renderable device node,
and for Wayland, the device path advertised is the one used by the
server for compositing.
From: Thierry Reding
If a device doesn't support rendering and support for PRIME isn't
enabled via the DRI_PRIME environment variable or dri.conf, attempt to
find a render node which can be used to offload rendering.
Signed-off-by: Thierry Reding
---
Along with platform and host1x bus support i
