On Thu, Nov 27, 2014 at 11:51:08AM -0500, Rob Clark wrote:
On Thu, Nov 27, 2014 at 11:39 AM, Thierry Reding
thierry.red...@gmail.com wrote:
Tegra K1 and later use a GPU that can be driven by the Nouveau driver.
But the GPU is a pure render node and has no display engine, hence the
scanout
On Fri, Nov 28, 2014 at 12:32:43AM -0500, Ilia Mirkin wrote:
On Thu, Nov 27, 2014 at 11:39 AM, Thierry Reding
thierry.red...@gmail.com wrote:
Tegra K1 and later use a GPU that can be driven by the Nouveau driver.
But the GPU is a pure render node and has no display engine, hence the
Hi,
On 28 November 2014 at 09:17, Thierry Reding thierry.red...@gmail.com
wrote:
On Fri, Nov 28, 2014 at 12:32:43AM -0500, Ilia Mirkin wrote: Also, can
you explain why it's advantageous for the setup to appear as
though it is a single device? i.e. what's wrong with just using
nouveau as a
Hi Thierry,
Must admit that I really prefer this idea over modifying existing
applications/users [1] because:
- Most of these setups are tightly coupled (imx+vivante, tegra+nouveau)
and pushing this down to the driver prevents duplication, and hardware
specific details in the users.
- Removes
Tegra K1 and later use a GPU that can be driven by the Nouveau driver.
But the GPU is a pure render node and has no display engine, hence the
scanout needs to happen on the Tegra display hardware. The GPU and the
display engine each have a separate DRM device node exposed by the
kernel.
To make
On Thu, Nov 27, 2014 at 11:39 AM, Thierry Reding
thierry.red...@gmail.com wrote:
Tegra K1 and later use a GPU that can be driven by the Nouveau driver.
But the GPU is a pure render node and has no display engine, hence the
scanout needs to happen on the Tegra display hardware. The GPU and the
On Thu, Nov 27, 2014 at 11:39 AM, Thierry Reding
thierry.red...@gmail.com wrote:
Tegra K1 and later use a GPU that can be driven by the Nouveau driver.
But the GPU is a pure render node and has no display engine, hence the
scanout needs to happen on the Tegra display hardware. The GPU and the
