From: Thomas Zimmermann <tzimmermann@suse.de>
To: Simon Ser <contact@emersion.fr>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/doc: document that PRIME import/export is always supported
Date: Thu, 13 Jul 2023 09:45:28 +0200 [thread overview]
Message-ID: <ecb43bcd-6907-e1e8-3c8c-63bde258c739@suse.de> (raw)
In-Reply-To: <F07F7XO3_lxljay8DZbVRbLevY3p4np8Pt11PsA_RWIV9Hkc1QKGlby5uBZPcCiQtEdLFBOjG0c2Sy528P3G3yNreQckRzFjWkNuPa-CNKY=@emersion.fr>
[-- Attachment #1.1: Type: text/plain, Size: 1089 bytes --]
Am 13.07.23 um 09:17 schrieb Simon Ser:
> On Thursday, July 13th, 2023 at 07:09, Thomas Zimmermann <tzimmermann@suse.de> wrote:
>
>>> + * Starting from kernel version 6.6, both &DRM_PRIME_CAP_IMPORT and
>>> + * &DRM_PRIME_CAP_EXPORT are always advertised.
>>> + *
>>
>> When people port these changes into their trees the version becomes
>> meaningless. There are so many "enterprise kernels" that combine whole
>> subsystems from different upstream releases.
>>
>> That makes me wonder if such documentation makes sense. We want to avoid
>> a situation where userspace does
>>
>> if (v6.6)
>> do()
>> else if (test_flags())
>> do()
>
> Daniel Vetter asked for specific kernel versions in b603e810f740
> ("drm/uapi: document kernel capabilities"). It allows user-space to
> figure out how widespread a cap is.
Well, OK then... :)
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-07-13 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 18:32 [PATCH] drm/doc: document that PRIME import/export is always supported Simon Ser
2023-07-12 18:37 ` Jeffrey Hugo
2023-07-13 5:09 ` Thomas Zimmermann
2023-07-13 7:17 ` Simon Ser
2023-07-13 7:45 ` Thomas Zimmermann [this message]
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=ecb43bcd-6907-e1e8-3c8c-63bde258c739@suse.de \
--to=tzimmermann@suse.de \
--cc=alexander.deucher@amd.com \
--cc=contact@emersion.fr \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=quic_jhugo@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox