view,
> but is hopefully a useful aid to, well, debugging.
>
> Cheers,
> Daniel
FWIW, I tested this on Tegra with some patches to the kernel to enable
the IN_FORMATS property and it all seems to work, so:
Tested-by: Thierry Reding <tred...@nvidia.com>
signature.asc
Description: P
On Mon, Feb 05, 2018 at 06:44:29PM +, Daniel Stone wrote:
> Use the new drmModeAddFB2WithModifiers interface to import buffers with
> modifiers.
>
> Signed-off-by: Daniel Stone
> Reviewed-by: Pekka Paalanen
> ---
> configure.ac
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
On Sat, Jun 21, 2014 at 01:37:16PM +0200, Rob Clark wrote:
On Fri, Jun 20, 2014 at 12:12 PM, James Thomas
james.tho...@codethink.co.uk wrote:
Update configure.ac to add check for libdrm_tegra
---
configure.ac | 18 ++
src/compositor-drm.c | 96
From: Thierry Reding tred...@nvidia.com
sizeof returns size_t, for which the correct printf specifier is %zu.
Fixes the following warning when building for ARMv7.
src/compositor-wayland.c: In function 'wayland_output_get_shm_buffer':
src/compositor-wayland.c:260:3: warning
From: Thierry Reding tred...@nvidia.com
When running the autogen.sh script, libtoolize complains thusly:
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac
and
libtoolize: rerunning libtoolize, to keep the correct libtool macros
in-tree.
libtoolize
On Tue, May 27, 2014 at 09:22:30AM +0300, Pekka Paalanen wrote:
On Mon, 19 May 2014 17:12:39 +0200
Thierry Reding thierry.red...@gmail.com wrote:
From: Thierry Reding tred...@nvidia.com
When cross-compiling, wayland-scanner cannot be used to generate files
because it is built
On Tue, May 27, 2014 at 09:43:09AM +0300, Pekka Paalanen wrote:
On Mon, 19 May 2014 17:12:40 +0200
Thierry Reding thierry.red...@gmail.com wrote:
From: Thierry Reding tred...@nvidia.com
This is mostly useless and can be confusing in makefiles. The pattern
rules defined in the makefile
On Thu, May 22, 2014 at 09:35:23AM -0700, Bill Spitzak wrote:
On 05/21/2014 03:09 PM, Thierry Reding wrote:
On Wed, May 21, 2014 at 02:54:36PM -0700, Bill Spitzak wrote:
On 05/21/2014 02:16 PM, Thierry Reding wrote:
While I agree with the other points, I think it's perfectly consistent
On Thu, May 22, 2014 at 09:25:40AM +0300, Pekka Paalanen wrote:
On Thu, 22 May 2014 00:18:23 +0200
Thierry Reding thierry.red...@gmail.com wrote:
On Wed, May 21, 2014 at 12:30:18PM +0300, Pekka Paalanen wrote:
On Tue, 20 May 2014 13:12:32 -0700 Bill Spitzak spit...@gmail.com wrote
On Tue, May 20, 2014 at 01:12:32PM -0700, Bill Spitzak wrote:
[...]
The biggest hint would be to print something with the word pkg-config in
it. Then I would have the secret password that would lead me to a man page
that would tell me what is going on.
Please print the package name the error
On Wed, May 21, 2014 at 12:17:29PM -0700, Bill Spitzak wrote:
On 05/21/2014 02:30 AM, Pekka Paalanen wrote:
[...]
Would that not cause the main build guide to become a mixture of
apt-get, emerge, yum, pacman, aptitude etc. commands? Where the
complete set of commands would never work on any
On Wed, May 21, 2014 at 12:30:18PM +0300, Pekka Paalanen wrote:
On Tue, 20 May 2014 13:12:32 -0700 Bill Spitzak spit...@gmail.com wrote:
[...]
I have to tell you that such one-line-at-a-time cut paste is
unbelievably tedious, and my biggest screwups when trying this on a
second machine
On Mon, May 19, 2014 at 11:59:51AM +0300, Pekka Paalanen wrote:
On Sun, 18 May 2014 00:39:16 +0200 Thierry Reding thierry.red...@gmail.com
wrote:
[...]
One issue here is that if --disable-scanner is specified, then the
wayland-scanner binary is neither built nor installed
On Mon, May 19, 2014 at 01:39:24PM +0300, Pekka Paalanen wrote:
On Mon, 19 May 2014 11:56:39 +0200 Thierry Reding thierry.red...@gmail.com
wrote:
On Mon, May 19, 2014 at 11:59:51AM +0300, Pekka Paalanen wrote:
On Sun, 18 May 2014 00:39:16 +0200 Thierry Reding
thierry.red...@gmail.com
From: Thierry Reding tred...@nvidia.com
The pkgdatadir variable is used to find data files installed by wayland.
If wayland is installed in a sysroot, the path to this directory needs
to be prefixed with the sysroot to make sure the proper files are found.
${pc_sysrootdir} is expanded
From: Thierry Reding tred...@nvidia.com
This is mostly useless and can be confusing in makefiles. The pattern
rules defined in the makefile snippet are generic enough to allow the
protocol sources to reside in subdirectories.
Signed-off-by: Thierry Reding tred...@nvidia.com
---
wayland
From: Thierry Reding tred...@nvidia.com
When cross-compiling, wayland-scanner cannot be used to generate files
because it is built for the host architecture. To overcome this, users
currently need to instruct the build not to create wayland-scanner and
provide a native variant in the PATH
From: Thierry Reding tred...@nvidia.com
When cross-compiling always look up the wayland-scanner binary in the
PATH. Using the value from the wayland-scanner.pc file will not work
because it will point to a binary built for the host.
While trying to find the path of the wayland-scanner makefile
From: Thierry Reding tred...@nvidia.com
To reduce code duplication and make sure it receives at minimum amount
of testing, use the wayland-scanner makefile snippet in this package.
Signed-off-by: Thierry Reding tred...@nvidia.com
---
Makefile.am | 9 +
1 file changed, 1 insertion(+), 8
On Fri, May 16, 2014 at 03:43:47PM +0530, Srivardhan Hebbar wrote:
This is a fix to the bug https://bugs.freedesktop.org/show_bug.cgi?id=78688.
Signed-off-by: Srivardhan Hebbar sri.heb...@samsung.com
---
configure.ac | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
From: Thierry Reding tred...@nvidia.com
The wayland-server-protocol.h and wayland-client-protocol.h headers are
currently being shipped in tarballs created using make dist. This causes
out-of-tree builds to fail since make will detect that the headers exist
by looking at the source directory (via
* Christopher Friedt wrote:
Hi folks,
I'm running into the following error when trying to launch demos.
terminal: symbol lookup error: /usr/lib64/egl/egl_gallium.so:
undefined symbol: wl_display_get_rgb_visual
The folllowing code snippet confirms that the symbol does not get
installed
Fixes the following build error in wayland-demos:
CCLD wayland-compositor
/usr/lib/libEGL.so: undefined reference to
`wayland_drm_buffer_get_buffer'
/usr/lib/libEGL.so: undefined reference to `wayland_drm_uninit'
/usr/lib/libEGL.so: undefined reference to
24 matches
Mail list logo