All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Ser <contact@emersion.fr>
To: "Marek Olšák" <maraeo@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v3] drm/fourcc: document modifier uniqueness requirements
Date: Fri, 29 May 2020 08:59:23 +0000	[thread overview]
Message-ID: <bbZABMxDckHUj5JW5DW0pSewqQ-rAIW0gvNnTlI4np7o1A2bDrpPGIeyk5tXGMDr_cAI1l_R9qw6ykJ8OEhQlbKruJ8IG579jqADaPAnUbA=@emersion.fr> (raw)
In-Reply-To: <CAAxE2A4NCo_KMkemUOHKbZ7P=GR4p-zwhpmP7Get18x4Ydb-Gg@mail.gmail.com>

On Thursday, May 28, 2020 5:49 PM, Marek Olšák <maraeo@gmail.com> wrote:

> On most hardware, there is a minimum pitch alignment for linear and
> any greater multiple of the alignment is fine.
>
> On Navi, the pitch in bytes for linear must be
> align(width * bpp / 8, 256). That's because the hw computes the pitch
> from the width and doesn't allow setting a custom pitch. For that
> reason, multi-GPU sharing might not be possible if the other GPU
> doesn't align the pitch in exactly the same way.

OK. In this case I think it's fine to make the DMA-BUF import fail, as
we've suggested on IRC. The more-or-less planned fix for these buffer
sharing issues is to revive the buffer constraints proposal from the
allocator project. It's a lot of work though.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-05-29  8:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 14:38 [PATCH v3] drm/fourcc: document modifier uniqueness requirements Simon Ser
2020-05-28 15:49 ` Marek Olšák
2020-05-29  8:59   ` Simon Ser [this message]
2020-05-29 13:28     ` Alex Deucher
2020-05-29 13:43       ` Daniel Vetter
2020-05-29 13:56       ` Daniel Stone
2020-05-29 14:29         ` Alex Deucher
2020-05-29 14:30           ` Daniel Stone
2020-05-29 14:36             ` Alex Deucher
2020-05-29 15:01               ` Daniel Stone
2020-05-29 15:31                 ` Alex Deucher
2020-05-30 13:08                 ` Michel Dänzer
2020-06-01 14:25                 ` Alex Deucher
2020-06-03  9:48                   ` Daniel Stone
2020-06-03 18:53                     ` Marek Olšák
2020-06-04  9:14                       ` Daniel Stone
2020-06-01 13:43         ` Neil Armstrong
2020-06-01 11:01 ` Brian Starkey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='bbZABMxDckHUj5JW5DW0pSewqQ-rAIW0gvNnTlI4np7o1A2bDrpPGIeyk5tXGMDr_cAI1l_R9qw6ykJ8OEhQlbKruJ8IG579jqADaPAnUbA=@emersion.fr' \
    --to=contact@emersion.fr \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maraeo@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.