Re: [Mesa-dev] Android + tegra + mesa

On Fri, Jan 18, 2019 at 01:26:30PM +0300, Artyom Bambalov wrote: > Do you have some notes on how to reproduce your setup? I've been meaning > to try this out but never found enough time to see it through. Having a > set of simple instructions for getting this built and booted would

Re: [Mesa-dev] Android + tegra + mesa

On Fri, Jan 18, 2019 at 12:28:07AM +0300, Artyom Bambalov wrote: > Hello, guys. I have device with tegra K1(T124). I try to get open source > graphical stack. What I use: mesa 3d(18.2-19.0), libdrm(2.4.96), > drm_hwcomposer(the latest), gbm_gralloc(the latest), 4.19 kernel by > google(tegra drm +

Re: [Mesa-dev] [PATCH mesa] meson: add missing tegra vdpau driver

; > > > > FtR, src/gallium/targets/vdpau/Makefile.am includes > > > > > src/gallium/drivers/tegra/Automake.inc which adds tegra to the > > > > > TARGET_DRIVERS, which in turn produces libvdpau_tegra.so > > > > > > > > > > If this was wr

Re: [Mesa-dev] [1/3] tegra: Remove usage of non-stable UAPI

On Tue, May 29, 2018 at 12:46:35PM +0200, Daniel Kolesa wrote: > Hello, > > On 2018/04/19 18:31, Thierry Reding wrote: > > From: Thierry Reding > > > > This code path is no longer required with framebuffer modifier support. > > This patch series fixes Xorg

[Mesa-dev] [PATCH 2/3] tegra: Fix scanout resources without modifiers

From: Thierry Reding <tred...@nvidia.com> Resources created for scanout but without modifiers need to be treated as pitch-linear. This is because applications that don't use modifiers to create resources must be assumed to not understand modifiers and in turn won't be able to create

[Mesa-dev] [PATCH 1/3] tegra: Remove usage of non-stable UAPI

From: Thierry Reding <tred...@nvidia.com> This code path is no longer required with framebuffer modifier support. Signed-off-by: Thierry Reding <tred...@nvidia.com> --- src/gallium/drivers/tegra/tegra_screen.c | 69 ++-- 1 file changed, 3 insertions(+),

[Mesa-dev] [PATCH 3/3] tegra: Treat resources with modifiers as scanout

From: Thierry Reding <tred...@nvidia.com> Resources created with modifiers are treated as scanout because there is no way for applications to specify the usage (though that capability may be useful to have in the future). Currently all the resources created by applications with mod

[Mesa-dev] [PATCH kmscube 3/4] Automatically select modifiers

From: Thierry Reding <tred...@nvidia.com> If available, use the formats/modifiers blob from a DRM/KMS device to automatically detect which modifiers to use. In the absence of the blob, leave it up to the implementation to choose an appropriate format. Based on work by Lucas Stach

[Mesa-dev] [PATCH kmscube 4/4] drm-atomic: Implement user interruption

From: Thierry Reding <tred...@nvidia.com> In legacy mode, the user can interrupt kmscube by pressing the return key. Implement the same behaviour for atomic mode. Signed-off-by: Thierry Reding <tred...@nvidia.com> --- drm-atomic.c | 25 + 1 file changed, 2

[Mesa-dev] [PATCH kmscube 2/4] Pass struct drm to init_gbm()

From: Thierry Reding <tred...@nvidia.com> This helps cut down on the number of parameters that we need to pass around. Subsequent patches will also add more data to struct drm that init_gbm() needs to access, so passing in the struct make sure these will be available. Based on work by

[Mesa-dev] [PATCH kmscube 1/4] drm-atomic: Fix indentation

From: Thierry Reding <tred...@nvidia.com> One of the error returns ended up being indented twice. Fix it. Signed-off-by: Thierry Reding <tred...@nvidia.com> --- drm-atomic.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm-atomic.c b/drm-atomic.c index

[Mesa-dev] [PATCH v5 6/6] autotools: Add tegra to AM_DISTCHECK_CONFIGURE_FLAGS

From: Thierry Reding <tred...@nvidia.com> This allows the driver to be built on a make distcheck and makes sure that it properly builds when a distribution tarball is made. Suggested-by: Emil Velikov <emil.veli...@collabora.com> Signed-off-by: Thierry Reding <tred...@nvidia.com>

[Mesa-dev] [PATCH v5 5/6] tegra: Initial support

r <a.hei...@gmail.com> Reviewed-by: Dmitry Osipenko <dig...@gmail.com> Reviewed-by: Dylan Baker <dy...@pnwbakers.com> Signed-off-by: Thierry Reding <tred...@nvidia.com> --- configure.ac | 12 +- include/drm-uapi/tegra_drm.h

[Mesa-dev] [PATCH v5 0/6] NVIDIA Tegra support

From: Thierry Reding <tred...@nvidia.com> This series of patches implements initial support for Tegra. The first two patches import DRM UAPI from v4.16-rc1 that provides framebuffer modifiers that can be used to specify buffers shared between Nouveau and the Tegra DRM driver. Patches 3 and

[Mesa-dev] [PATCH v5 4/6] nouveau: Add framebuffer modifier support

From: Thierry Reding <tred...@nvidia.com> This adds support for framebuffer modifiers to Nouveau. This will be used by the Tegra driver to share metadata about the format of buffers (such as the tiling mode or compression). Changes in v2: - remove unused parameters to nouveau_buffer_

[Mesa-dev] [PATCH v5 2/6] drm/tegra: Sanitize format modifiers

From: Thierry Reding <tred...@nvidia.com> The existing format modifier definitions were merged prematurely, and recent work has unveiled that the definitions are suboptimal in several ways: - The format specifiers, except for one, are not Tegra specific, but the names don't r

[Mesa-dev] [PATCH v5 3/6] nouveau/nvc0: Extract common tile mode macro

From: Thierry Reding <tred...@nvidia.com> Add a new macro that can be used to extract the tiling mode from a tile_mode value. This is will be used to determine the number of GOBs used in block linear mode. Acked-by: Emil Velikov <emil.veli...@collabora.com> Tested-by: Andre H

[Mesa-dev] [PATCH v5 1/6] drm/fourcc: Fix fourcc_mod_code() definition

From: Thierry Reding <tred...@nvidia.com> Avoid a compiler warnings when the val parameter is an expression. This is based on commit 5843f4e02fbe86a59981e35adc6cabebee46fdc0 from Linux v4.16-rc1. Acked-by: Emil Velikov <emil.veli...@collabora.com> Tested-by: Andre Heider <a.h

Re: [Mesa-dev] [PATCH v4 4/6] nouveau: Add framebuffer modifier support

On Wed, Mar 07, 2018 at 01:15:35PM -0500, Ilia Mirkin wrote: > On Wed, Mar 7, 2018 at 10:53 AM, Thierry Reding > <thierry.red...@gmail.com> wrote: > > From: Thierry Reding <tred...@nvidia.com> > > > > This adds support for framebuffer modifiers to Nouveau. This

Re: [Mesa-dev] [PATCH] glx/apple: Ship meson build file in tarball

On Wed, Mar 07, 2018 at 10:08:59AM -0800, Dylan Baker wrote: > Quoting Thierry Reding (2018-03-07 07:55:37) > > From: Thierry Reding <tred...@nvidia.com> > > > > The meson build file for Apple GLX is not listed in the EXTRA_DIST make > > variable and therefore isn

[Mesa-dev] [PATCH] glx/apple: Ship meson build file in tarball

From: Thierry Reding <tred...@nvidia.com> The meson build file for Apple GLX is not listed in the EXTRA_DIST make variable and therefore isn't shipped as part of the release tarball, so meson builds from the tarball will fail. Add the file to EXTRA_DIST to ensure it is included in the t

[Mesa-dev] [PATCH v4 5/6] tegra: Initial support

r <a.hei...@gmail.com> Reviewed-by: Dmitry Osipenko <dig...@gmail.com> Signed-off-by: Thierry Reding <tred...@nvidia.com> --- configure.ac | 12 +- include/drm-uapi/tegra_drm.h | 225 meson.build

[Mesa-dev] [PATCH v4 1/6] drm/fourcc: Fix fourcc_mod_code() definition

From: Thierry Reding <tred...@nvidia.com> Avoid a compiler warnings when the val parameter is an expression. This is based on commit 5843f4e02fbe86a59981e35adc6cabebee46fdc0 from Linux v4.16-rc1. Acked-by: Emil Velikov <emil.veli...@collabora.com> Tested-by: Andre Heider <a.h

[Mesa-dev] [PATCH v4 6/6] autotools: Add tegra to AM_DISTCHECK_CONFIGURE_FLAGS

From: Thierry Reding <tred...@nvidia.com> This allows the driver to be built on a make distcheck and makes sure that it properly builds when a distribution tarball is made. Suggested-by: Emil Velikov <emil.veli...@collabora.com> Signed-off-by: Thierry Reding <tred...@nvidia.com>

[Mesa-dev] [PATCH v4 4/6] nouveau: Add framebuffer modifier support

From: Thierry Reding <tred...@nvidia.com> This adds support for framebuffer modifiers to Nouveau. This will be used by the Tegra driver to share metadata about the format of buffers (such as the tiling mode or compression). Changes in v2: - remove unused parameters to nouveau_buffer_

[Mesa-dev] [PATCH v4 3/6] nouveau/nvc0: Extract common tile mode macro

From: Thierry Reding <tred...@nvidia.com> Add a new macro that can be used to extract the tiling mode from a tile_mode value. This is will be used to determine the number of GOBs used in block linear mode. Acked-by: Emil Velikov <emil.veli...@collabora.com> Tested-by: Andre H

[Mesa-dev] [PATCH v4 2/6] drm/tegra: Sanitize format modifiers

From: Thierry Reding <tred...@nvidia.com> The existing format modifier definitions were merged prematurely, and recent work has unveiled that the definitions are suboptimal in several ways: - The format specifiers, except for one, are not Tegra specific, but the names don't r

[Mesa-dev] [PATCH v4 0/6] NVIDIA Tegra support

From: Thierry Reding <tred...@nvidia.com> This series of patches implements initial support for Tegra. The first two patches import DRM UAPI from v4.16-rc1 that provides framebuffer modifiers that can be used to specify buffers shared between Nouveau and the Tegra DRM driver. Patches 3 and

Re: [Mesa-dev] [PATCH v2] loader: Add support for platform and host1x busses

On Fri, Mar 02, 2018 at 01:31:22PM +, Emil Velikov wrote: > On 2 March 2018 at 11:29, Thierry Reding <thierry.red...@gmail.com> wrote: > > From: Thierry Reding <tred...@nvidia.com> > > > > ARM SoCs usually have their DRM/KMS devices on the platform bus, so add

Re: [Mesa-dev] [PATCH v3 5/6] tegra: Initial support

On Thu, Mar 01, 2018 at 09:10:39AM -0800, Dylan Baker wrote: > Quoting Thierry Reding (2018-03-01 05:54:53) > > --- /dev/null > > +++ b/src/gallium/winsys/tegra/drm/meson.build > > @@ -0,0 +1,33 @@ > > +# Copyright © 2018 NVIDIA CORPORATION > > + > > +# Permi

Re: [Mesa-dev] [PATCH v3 4/6] nouveau: Add framebuffer modifier support

On Fri, Mar 02, 2018 at 12:28:02PM +, Daniel Stone wrote: > Hi, > > On 2 March 2018 at 12:06, Thierry Reding <thierry.red...@gmail.com> wrote: > > On Thu, Mar 01, 2018 at 09:37:28AM -0500, Ilia Mirkin wrote: > >> > +static void > >> > +nvc0_quer

Re: [Mesa-dev] [PATCH v3 5/6] tegra: Initial support

On Thu, Mar 01, 2018 at 09:41:37AM -0500, Ilia Mirkin wrote: > Is this substantially different than the renderonly helper? i.e. could > you reuse it somehow? (If not, that's fine too, just asking.) Yeah, this is fairly different from renderonly in that it completely wraps another driver.

Re: [Mesa-dev] [PATCH v3 4/6] nouveau: Add framebuffer modifier support

On Thu, Mar 01, 2018 at 09:04:58AM -0800, Dylan Baker wrote: > Quoting Thierry Reding (2018-03-01 05:54:52) > > From: Thierry Reding <tred...@nvidia.com> > > > > This adds support for framebuffer modifiers to Nouveau. This will be > > used by the Tegra driver t

Re: [Mesa-dev] [PATCH v3 4/6] nouveau: Add framebuffer modifier support

On Thu, Mar 01, 2018 at 09:37:28AM -0500, Ilia Mirkin wrote: > On Thu, Mar 1, 2018 at 8:54 AM, Thierry Reding <thierry.red...@gmail.com> > wrote: > > From: Thierry Reding <tred...@nvidia.com> > > > > This adds support for framebuffer modifiers to Nouveau. This

[Mesa-dev] [PATCH v2] loader: Add support for platform and host1x busses

From: Thierry Reding <tred...@nvidia.com> ARM SoCs usually have their DRM/KMS devices on the platform bus, so add support for this bus in order to allow use of the DRI_PRIME environment variable with those devices. While at it, also support the host1x bus, which is effectively the same bu

Re: [Mesa-dev] [PATCH v2] disk cache: Link with -latomic if necessary

On Thu, Mar 01, 2018 at 08:53:59AM -0800, Dylan Baker wrote: > Quoting Thierry Reding (2018-03-01 05:28:07) > > From: Thierry Reding <tred...@nvidia.com> > > > > The disk cache implementation uses 64-bit atomic operations. For some > > architectures, such as

Re: [Mesa-dev] [PATCH] loader: Add support for platform and host1x busses

On Thu, Mar 01, 2018 at 02:14:41PM +, Eric Engestrom wrote: > > > On March 1, 2018 1:31:53 PM UTC, Thierry Reding <thierry.red...@gmail.com> > wrote: > > From: Thierry Reding <tred...@nvidia.com> > > > > ARM SoCs usually have their DRM/K

[Mesa-dev] [PATCH v3 6/6] autotools: Add tegra to AM_DISTCHECK_CONFIGURE_FLAGS

From: Thierry Reding <tred...@nvidia.com> This allows the driver to be built on a make distcheck and makes sure that it properly builds when a distribution tarball is made. Suggested-by: Emil Velikov <emil.veli...@collabora.com> Signed-off-by: Thierry Reding <tred...@nvidia.com>

[Mesa-dev] [PATCH v3 4/6] nouveau: Add framebuffer modifier support

From: Thierry Reding <tred...@nvidia.com> This adds support for framebuffer modifiers to Nouveau. This will be used by the Tegra driver to share metadata about the format of buffers (such as the tiling mode or compression). Changes in v2: - remove unused parameters to nouveau_buffer_

[Mesa-dev] [PATCH v3 3/6] nouveau/nvc0: Extract common tile mode macro

From: Thierry Reding <tred...@nvidia.com> Add a new macro that can be used to extract the tiling mode from a tile_mode value. This is will be used to determine the number of GOBs used in block linear mode. Acked-by: Emil Velikov <emil.veli...@collabora.com> Tested-by: Andre H

[Mesa-dev] [PATCH v3 5/6] tegra: Initial support

ge on pre-Tegra124 - support X without explicit PRIME Reviewed-by: Emil Velikov <emil.veli...@collabora.com> Acked-by: Emil Velikov <emil.veli...@collabora.com> Tested-by: Andre Heider <a.hei...@gmail.com> Signed-off-by: Thierry Reding <tred...

[Mesa-dev] [PATCH v3 0/6] NVIDIA Tegra support

From: Thierry Reding <tred...@nvidia.com> This series of patches implements initial support for Tegra. The first two patches import DRM UAPI from v4.16-rc1 that provides framebuffer modifiers that can be used to specify buffers shared between Nouveau and the Tegra DRM driver. Patches 3 and

[Mesa-dev] [PATCH v3 2/6] drm/tegra: Sanitize format modifiers

From: Thierry Reding <tred...@nvidia.com> The existing format modifier definitions were merged prematurely, and recent work has unveiled that the definitions are suboptimal in several ways: - The format specifiers, except for one, are not Tegra specific, but the names don't r

[Mesa-dev] [PATCH v3 1/6] drm/fourcc: Fix fourcc_mod_code() definition

From: Thierry Reding <tred...@nvidia.com> Avoid a compiler warnings when the val parameter is an expression. This is based on commit 5843f4e02fbe86a59981e35adc6cabebee46fdc0 from Linux v4.16-rc1. Acked-by: Emil Velikov <emil.veli...@collabora.com> Tested-by: Andre Heider <a.h

[Mesa-dev] [PATCH] loader: Add support for platform and host1x busses

From: Thierry Reding <tred...@nvidia.com> ARM SoCs usually have their DRM/KMS devices on the platform bus, so add support for this bus in order to allow use of the DRI_PRIME environment variable with those devices. While at it, also support the host1x bus, which is effectively the same bu

[Mesa-dev] [PATCH v2] disk cache: Link with -latomic if necessary

From: Thierry Reding <tred...@nvidia.com> The disk cache implementation uses 64-bit atomic operations. For some architectures, such as 32-bit ARM, GCC will not be able to translate these operations into atomic, lock-free instructions and will instead rely on the external atomics l

Re: [Mesa-dev] [PATCH] disk cache: Link with -latomic if necessary

On Mon, Feb 26, 2018 at 11:28:23PM +, Mike Lothian wrote: > On Fri, 23 Feb 2018 at 13:18 Thierry Reding <thierry.red...@gmail.com> > wrote: > > > From: Thierry Reding <tred...@nvidia.com> > > > > The disk cache implementation uses 64-bit atomic

Re: [Mesa-dev] [PATCH] disk cache: Link with -latomic if necessary

On Mon, Feb 26, 2018 at 12:05:51PM -0800, Dylan Baker wrote: > Quoting Thierry Reding (2018-02-23 05:18:28) > > From: Thierry Reding <tred...@nvidia.com> > > > > The disk cache implementation uses 64-bit atomic operations. For some > > architectures, such as

Re: [Mesa-dev] [PATCH] disk cache: Link with -latomic if necessary

On Mon, Feb 26, 2018 at 11:14:05AM -0800, Matt Turner wrote: > On Fri, Feb 23, 2018 at 5:18 AM, Thierry Reding > <thierry.red...@gmail.com> wrote: > > From: Thierry Reding <tred...@nvidia.com> > > > > The disk cache implementation uses 64-bit atomic op

Re: [Mesa-dev] [PATCH 5/5] tegra: Initial support

On Thu, Feb 22, 2018 at 02:32:26PM +, Emil Velikov wrote: > On 22 February 2018 at 13:23, Thierry Reding <thierry.red...@gmail.com> wrote: [...] > > Good point. Let me check what exactly we use in the closed-source driver > > and then come up with a proposal. > >

[Mesa-dev] [PATCH] disk cache: Link with -latomic if necessary

From: Thierry Reding <tred...@nvidia.com> The disk cache implementation uses 64-bit atomic operations. For some architectures, such as 32-bit ARM, GCC will not be able to translate these operations into lock-free instructions and will instead rely on the external atomics library to p

[Mesa-dev] [PATCH v2 5/6] tegra: Initial support

OURCES variable - drop unneeded tegra/ prefix for includes - open device files with O_CLOEXEC - update copyrights Reviewed-by: Emil Velikov <emil.veli...@collabora.com> Acked-by: Emil Velikov <emil.veli...@collabora.com> Tested-by: Andre Heider <a.hei...@gmail.com> Signed-off-

[Mesa-dev] [PATCH v2 6/6] autotools: Add tegra to AM_DISTCHECK_CONFIGURE_FLAGS

From: Thierry Reding <tred...@nvidia.com> This allows the driver to be built on a make distcheck and makes sure that it properly builds when a distribution tarball is made. Suggested-by: Emil Velikov <emil.veli...@collabora.com> Signed-off-by: Thierry Reding <tred...@nvidia.com>

[Mesa-dev] [PATCH v2 3/6] nouveau/nvc0: Extract common tile mode macro

From: Thierry Reding <tred...@nvidia.com> Add a new macro that can be used to extract the tiling mode from a tile_mode value. This is will be used to determine the number of GOBs used in block linear mode. Acked-by: Emil Velikov <emil.veli...@collabora.com> Tested-by: Andre H

[Mesa-dev] [PATCH v2 4/6] nouveau: Add framebuffer modifier support

From: Thierry Reding <tred...@nvidia.com> This adds support for framebuffer modifiers to Nouveau. This will be used by the Tegra driver to share metadata about the format of buffers (such as the tiling mode or compression). Changes in v2: - remove unused parameters to nouveau_buffer_

[Mesa-dev] [PATCH v2 1/6] drm/fourcc: Fix fourcc_mod_code() definition

From: Thierry Reding <tred...@nvidia.com> Avoid a compiler warnings when the val parameter is an expression. This is based on commit 5843f4e02fbe86a59981e35adc6cabebee46fdc0 from Linux v4.16-rc1. Acked-by: Emil Velikov <emil.veli...@collabora.com> Tested-by: Andre Heider <a.h

[Mesa-dev] [PATCH v2 2/6] drm/tegra: Sanitize format modifiers

From: Thierry Reding <tred...@nvidia.com> The existing format modifier definitions were merged prematurely, and recent work has unveiled that the definitions are suboptimal in several ways: - The format specifiers, except for one, are not Tegra specific, but the names don't r

[Mesa-dev] [PATCH v2 0/6] NVIDIA Tegra support

From: Thierry Reding <tred...@nvidia.com> This series of patches implements initial support for Tegra. The first two patches import DRM UAPI from v4.16-rc1 that provide framebuffer modifiers that can be used to specify buffers shared between Nouveau and the Tegra DRM driver. Patches 3 and

[Mesa-dev] [PATCH] fixup! tegra: Initial support

From: Thierry Reding <tred...@nvidia.com> --- configure.ac| 5 +++-- src/gallium/drivers/tegra/Makefile.am | 9 +--- src/gallium/drivers/tegra/Makefile.sources | 5 - src/gallium/drivers/tegra/tegra_context.c | 8 +++---

[Mesa-dev] [PATCH] fixup! nouveau: Add framebuffer modifier support

From: Thierry Reding <tred...@nvidia.com> --- src/gallium/drivers/nouveau/nouveau_buffer.c | 3 +- src/gallium/drivers/nouveau/nouveau_buffer.h | 3 +- src/gallium/drivers/nouveau/nouveau_screen.c | 10 --- src/gallium/drivers/nouveau/nv30/nv30_resource.c | 4 +- src/g

Re: [Mesa-dev] [PATCH 5/5] tegra: Initial support

On Thu, Feb 22, 2018 at 02:31:48PM +0100, Erik Faye-Lund wrote: > On Thu, Feb 22, 2018 at 2:23 PM, Thierry Reding > <thierry.red...@gmail.com> wrote: > > On Wed, Feb 21, 2018 at 05:01:02PM +, Emil Velikov wrote: > >> Hi Thierry, > >> > >>

Re: [Mesa-dev] [PATCH 5/5] tegra: Initial support

On Wed, Feb 21, 2018 at 05:01:02PM +, Emil Velikov wrote: > Hi Thierry, > > On 21 February 2018 at 15:30, Thierry Reding <thierry.red...@gmail.com> wrote: > > > @@ -2595,6 +2596,11 @@ if test -n "$with_gallium_drivers"; then > > xim

Re: [Mesa-dev] [PATCH 4/5] nouveau: Add framebuffer modifier support

On Wed, Feb 21, 2018 at 04:37:45PM +, Emil Velikov wrote: > Hi Thierry, > > On 21 February 2018 at 15:30, Thierry Reding <thierry.red...@gmail.com> wrote: > > > > > struct pipe_resource * > > nouveau_buffer_create(struct pipe_screen *pscreen, >

Re: [Mesa-dev] [PATCH 4/5] nouveau: Add framebuffer modifier support

On Wed, Feb 21, 2018 at 11:05:45AM -0500, Ilia Mirkin wrote: > On Wed, Feb 21, 2018 at 10:30 AM, Thierry Reding > <thierry.red...@gmail.com> wrote: > > From: Thierry Reding <tred...@nvidia.com> > > > > This adds support for framebuffer modifiers to Nouveau

[Mesa-dev] [PATCH 5/5] tegra: Initial support

.st>. Signed-off-by: Thierry Reding <tred...@nvidia.com> --- configure.ac | 11 +- include/drm-uapi/tegra_drm.h | 225 meson.build|7 +- src/gallium

[Mesa-dev] [PATCH 3/5] nouveau/nvc0: Extract common tile mode macro

From: Thierry Reding <tred...@nvidia.com> Add a new macro that can be used to extract the tiling mode from a tile_mode value. This is will be used to determine the number of GOBs used in block linear mode. Signed-off-by: Thierry Reding <tred...@nvidia.com> --- src/gallium/drivers/

[Mesa-dev] [PATCH 4/5] nouveau: Add framebuffer modifier support

From: Thierry Reding <tred...@nvidia.com> This adds support for framebuffer modifiers to Nouveau. This will be used by the Tegra driver to share metadata about the format of buffers (such as the tiling mode or compression). Signed-off-by: Thierry Reding <tred...@nvidia.com> ---

[Mesa-dev] [PATCH 2/5] drm/tegra: Sanitize format modifiers

From: Thierry Reding <tred...@nvidia.com> The existing format modifier definitions were merged prematurely, and recent work has unveiled that the definitions are suboptimal in several ways: - The format specifiers, except for one, are not Tegra specific, but the names don't r

[Mesa-dev] [PATCH 0/5] NVIDIA Tegra support

From: Thierry Reding <tred...@nvidia.com> This series of patches implements initial support for Tegra. The first two patches import DRM UAPI from v4.16-rc1 that provide framebuffer modifiers that can be used to specify buffers shared between Nouveau and the Tegra DRM driver. Patches 3 and

[Mesa-dev] [PATCH 1/5] drm/fourcc: Fix fourcc_mod_code() definition

From: Thierry Reding <tred...@nvidia.com> Avoid a compiler warnings when the val parameter is an expression. This is based on commit 5843f4e02fbe86a59981e35adc6cabebee46fdc0 from Linux v4.16-rc1. Signed-off-by: Thierry Reding <tred...@nvidia.com> --- include/drm-uapi/drm_fourcc

[Mesa-dev] [PATCH libdrm 1/2] drm/fourcc: Fix fourcc_mod_code() definition

From: Thierry Reding <tred...@nvidia.com> Avoid compiler warnings when the val parameter is an expression. Signed-off-by: Thierry Reding <tred...@nvidia.com> --- include/drm/drm_fourcc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm_fourcc.h b

[Mesa-dev] [PATCH libdrm 0/2] drm/tegra: Sanitize format modifiers

From: Thierry Reding <tred...@nvidia.com> These UABI changes have now been merged into drm-next, so synchronize the libdrm headers and fixup the format modifiers in modetest. Thierry Thierry Reding (2): drm/fourcc: Fix fourcc_mod_code() definition drm/tegra: Sanitize format mod

[Mesa-dev] [PATCH libdrm 2/2] drm/tegra: Sanitize format modifiers

From: Thierry Reding <tred...@nvidia.com> The existing format modifier definitions were merged prematurely, and recent work has unveiled that the definitions are suboptimal in several ways: - The format specifiers, except for one, are not Tegra specific, but the names don't r

[Mesa-dev] [PATCH] nouveau: Support fence FDs

From: Thierry Reding <tred...@nvidia.com> Implements fence FDs based on new libdrm API and the accompanying IOCTL. Signed-off-by: Thierry Reding <tred...@nvidia.com> --- For the kernel patches that add the new IOCTL, see the series at: https://patchwork.freedesktop.org/

Re: [Mesa-dev] [PATCH v2 3/3] imx: gallium driver for imx-drm scanout driver

On Fri, Dec 23, 2016 at 11:04:51PM +0100, Christian Gmeiner wrote: [...] > +struct pipe_screen *imx_drm_screen_create(int fd) > +{ > + struct renderonly ro = { > + .create_for_resource = renderonly_create_kms_dumb_buffer_for_resource, > + .kms_fd = fd, > + .gpu_fd =

Re: [Mesa-dev] [RFC] loader: Automatic PRIME detection

). Thierry > On 23/12/2016 21:36, Thierry Reding wrote: > > From: Thierry Reding <tred...@nvidia.com> > > > > 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 > > f

[Mesa-dev] [RFC] loader: Automatic PRIME detection

From: Thierry Reding <tred...@nvidia.com> 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 <tred...@n

[Mesa-dev] [PATCH 1/2] loader: Add support for USB devices

From: Thierry Reding <tred...@nvidia.com> Allow USB devices to be used as output slaves for PRIME. Note that this currently doesn't work on the X.Org server's built-in modesetting driver because it requires glamor in order to expose the necessary capabilities through RandR. It should be po

[Mesa-dev] [PATCH 2/2] loader: Add support for platform and host1x busses

From: Thierry Reding <tred...@nvidia.com> ARM SoCs usually have their DRM/KMS devices on the platform bus, so add support for this bus in order to allow use of the DRI_PRIME environment variable with those devices. While at it, also support the host1x bus, which is effectively the same bu

Re: [Mesa-dev] [PATCH] loader: Add vim modeline

r and per directory, and they all require manual intervention to activate. Most are insecure to the point where I wouldn't want to enable them. Thierry > On Dec 21, 2016 8:44 AM, "Thierry Reding" <thierry.red...@gmail.com> wrote: > > From: Thierry Reding <tred..

[Mesa-dev] [PATCH] loader: Add vim modeline

From: Thierry Reding <tred...@nvidia.com> Add a vim modeline that defines the identation style used in this file. This is useful to avoid vim's defaults (8-column tabs) from getting in the way. While at it, fix up a few cases where inconsistent indentation is used. Signed-off-by: Thierry

Re: [Mesa-dev] [PATCH 1/3] gallium: add renderonly library

On Mon, Dec 19, 2016 at 08:54:04PM +0100, Christian Gmeiner wrote: > 2016-12-19 14:08 GMT+01:00 Thierry Reding <thierry.red...@gmail.com>: > > On Wed, Nov 30, 2016 at 02:44:34PM +0100, Christian Gmeiner wrote: [...] > >> GALLIUM_WINSYS_CFLAGS = \ > >> -I

Re: [Mesa-dev] [PATCH 3/3] imx: gallium driver for imx-drm scanout driver

On Mon, Dec 19, 2016 at 04:04:34PM +, Emil Velikov wrote: > On Monday, 19 December 2016, Thierry Reding <thierry.red...@gmail.com> > wrote: > > > On Wed, Nov 30, 2016 at 02:44:36PM +0100, Christian Gmeiner wrote: > > [...] > > > +static struct pipe

Re: [Mesa-dev] [PATCH 3/3] imx: gallium driver for imx-drm scanout driver

On Wed, Nov 30, 2016 at 02:44:36PM +0100, Christian Gmeiner wrote: [...] > +static struct pipe_screen *imx_open_render_node(struct renderonly *ro) > +{ > + return etna_drm_screen_create_rendernode(ro); > +} Patch 2/3 never made it into my inbox for some reason, and had to find it in some

Re: [Mesa-dev] [PATCH 1/3] gallium: add renderonly library

On Wed, Nov 30, 2016 at 02:44:34PM +0100, Christian Gmeiner wrote: > This a very lightweight library to add basic support for > renderonly GPUs. It does all the magic regarding in/exporting > buffers etc. This library will likely break android support and > hopefully will get replaced with a

Re: [Mesa-dev] [PATCH 3/3] imx: gallium driver for imx-drm scanout driver

On Thu, Dec 01, 2016 at 03:00:20PM +, Emil Velikov wrote: > On 30 November 2016 at 13:44, Christian Gmeiner > wrote: > > The imx (stub) driver is needed to get hardware acceleration from > > etnaviv on a platform using imx-drm kms driver. This adds support > > for

Re: [Mesa-dev] [PATCH RFC 0/2] GBM API extension to support fusing KMS and render devices

On Mon, Mar 07, 2016 at 10:46:52AM +0100, Lucas Stach wrote: > Am Freitag, den 04.03.2016, 18:34 + schrieb Emil Velikov: > > On 4 March 2016 at 17:38, Lucas Stach wrote: > > > Am Freitag, den 04.03.2016, 17:20 + schrieb Daniel Stone: > > >> Hi, > > >> > > >> On 4

Re: [Mesa-dev] [RFC 1/2] gallium: add renderonly driver

On Fri, Oct 16, 2015 at 12:09:52AM +0100, Emil Velikov wrote: > Hi Christian, > > I'm glad to see Thierry's work revived. Hopefully this will soon be > the basis of many more drivers. > > On 11 October 2015 at 16:09, Christian Gmeiner > wrote: > > This commit adds a

Re: [Mesa-dev] [RFC 1/2] gallium: add renderonly driver

Hi Christian, First off, thanks for reviving this effort. It's been one of the things that I've had nagging at me for much too long and I think it needs to be solved. So I'm hopeful that the more people we get looking at this the more likely it will be to come up with a solution that works well

Re: [Mesa-dev] Valve games for Mesa/DRI developers

Hi Daniel, I'm not much of a gamer myself, but I imagine that these games would be useful, real-life tests and/or entertaining benchmarks. Given that I work mostly on ARM systems, do you know if there are any plans on making these games available on ARM? I know some of Valve's games have been

Re: [Mesa-dev] FOSDEM15: Graphics DevRoom: call for speakers.

On Tue, Dec 09, 2014 at 03:39:26PM +0100, Luc Verhaegen wrote: On Thu, Oct 02, 2014 at 07:44:57PM +0200, Luc Verhaegen wrote: Hi, At FOSDEM on the 31st of january and the 1st of February 2015, there will be another graphics DevRoom. URL: https://fosdem.org/2015/ Slots will be handed

Re: [Mesa-dev] [RFC] tegra: Initial support

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

Re: [Mesa-dev] [Nouveau] [RFC] tegra: Initial support

On Fri, Nov 28, 2014 at 02:14:24PM +0900, Alexandre Courbot wrote: On 11/28/2014 01:39 AM, Thierry Reding 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

Re: [Mesa-dev] [RFC] tegra: Initial support

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

Re: [Mesa-dev] [Nouveau] [RFC] tegra: Initial support

On Fri, Nov 28, 2014 at 05:52:26PM +0900, Alexandre Courbot wrote: On Fri, Nov 28, 2014 at 5:48 PM, Thierry Reding thierry.red...@gmail.com wrote: On Fri, Nov 28, 2014 at 02:14:24PM +0900, Alexandre Courbot wrote: On 11/28/2014 01:39 AM, Thierry Reding wrote: Tegra K1 and later use a GPU

[Mesa-dev] [RFC] tegra: Initial support

for creating a screen - implement enough support to seamlessly integrate with X - refactor some of the code to be reusable by other drivers Signed-off-by: Thierry Reding tred...@nvidia.com --- configure.ac | 12 +- src/gallium/Makefile.am

Re: [Mesa-dev] [PATCH] dri/kms: Always zero out struct drm_mode_create_dumb

On Sun, Nov 16, 2014 at 01:37:52AM +, Emil Velikov wrote: On 13/11/14 18:05, Thierry Reding wrote: From: Thierry Reding tred...@nvidia.com The DRM_IOCTL_MODE_CREATE_DUMB (and others) IOCTL isn't very rigorously specified, which has the effect that some kernel drivers do not consider

Re: [Mesa-dev] [PATCH] Mark debug_print with __attribute__ ((format(__printf__, 1, 0)))

On Sun, Jan 12, 2014 at 10:34:19AM -0800, Keith Packard wrote: the drmServerInfo member, debug_print, takes a printf format string and varargs list. Tell the compiler about it. Signed-off-by: Keith Packard kei...@keithp.com --- xf86drm.h | 8 +++- 1 file changed, 7 insertions(+), 1

Re: [Mesa-dev] rules for merging patches to libdrm

On Mon, Nov 18, 2013 at 01:38:55PM -0500, Jerome Glisse wrote: On Mon, Nov 18, 2013 at 05:41:50PM +0100, Thierry Reding wrote: On Mon, Nov 18, 2013 at 11:21:36AM -0500, Rob Clark wrote: On Mon, Nov 18, 2013 at 10:23 AM, Thierry Reding thierry.red...@gmail.com wrote: On Mon, Nov 18

Re: [Mesa-dev] rules for merging patches to libdrm

On Sat, Nov 09, 2013 at 01:26:24PM -0800, Ian Romanick wrote: On 11/09/2013 12:11 AM, Dave Airlie wrote: How does this interact with the rule that kernel interfaces require an open source userspace? Is here are the mesa/libdrm patches that use it sufficient to get the kernel interface

  1   2   >