From: Daniel Stone <daniels@collabora.com>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH libdrm 2/2] headers: Update README
Date: Fri, 30 Mar 2018 13:28:50 +0100 [thread overview]
Message-ID: <20180330122850.12134-2-daniels@collabora.com> (raw)
In-Reply-To: <20180330122850.12134-1-daniels@collabora.com>
Nouveau has made a very deliberate choice to hide its actual kernel ABI
behind libdrm. i915 is no longer out of date.
Signed-off-by: Daniel Stone <daniels@collabora.com>
---
include/drm/README | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/include/drm/README b/include/drm/README
index 5b518ddf..b4658dd7 100644
--- a/include/drm/README
+++ b/include/drm/README
@@ -91,14 +91,10 @@ Most UMS headers:
Status: ?
Promote to fixed size ints, which match the current (32bit) ones.
-i915_drm.h
- - Missing PARAMS - HAS_POOLED_EU, MIN_EU_IN_POOL CONTEXT_PARAM_NO_ERROR_CAPTURE
-Status: Trivial.
-
nouveau_drm.h
- Missing macros NOUVEAU_GETPARAM*, NOUVEAU_DRM_HEADER_PATCHLEVEL, structs,
enums
-Status: ?
+Status: Deliberate UABI choice; nouveau hides the exact kernel ABI behind libdrm
r128_drm.h
- Broken compat ioctls.
--
2.16.2
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-03-30 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 12:28 [PATCH libdrm 1/2] headers: Sync with drm-next Daniel Stone
2018-03-30 12:28 ` Daniel Stone [this message]
2018-03-30 13:29 ` [PATCH libdrm 2/2] headers: Update README Alex Deucher
2018-03-30 13:30 ` [PATCH libdrm 1/2] headers: Sync with drm-next Alex Deucher
2018-03-30 15:11 ` Daniel Stone
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=20180330122850.12134-2-daniels@collabora.com \
--to=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
/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