From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90898] Provide DRM_MODE_FB_DIRTY_MAX_CLIPS in drm_mode.h
Date: Mon, 08 Jun 2015 21:36:59 +0000 [thread overview]
Message-ID: <bug-90898-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1024 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90898
Bug ID: 90898
Summary: Provide DRM_MODE_FB_DIRTY_MAX_CLIPS in drm_mode.h
Product: DRI
Version: XOrg git
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
Assignee: dri-devel@lists.freedesktop.org
Reporter: lampersperger.andreas@heidenhain.de
When calling drmModeDirtyFB on linux, it fails when num_clips are more than
DRM_MODE_FB_DIRTY_MAX_CLIPS (value: 256). But there is no way to check this for
xf86-video-* drivers, because when including drm_mode.h, you get the drm_mode.h
from /usr/include/libdrm/drm_mode.h and not /usr/include/drm/drm_mode.h.
Please add
#define DRM_MODE_FB_DIRTY_MAX_CLIPS 256
to your drm_mode.h, to allow xf86-video-* drivers to check parameters before
calling drmModeDirtyFB(...).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2253 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-06-08 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 21:36 bugzilla-daemon [this message]
2015-06-09 8:03 ` [Bug 90898] Provide DRM_MODE_FB_DIRTY_MAX_CLIPS in drm_mode.h bugzilla-daemon
2015-06-09 13:07 ` bugzilla-daemon
2016-12-12 13:31 ` bugzilla-daemon
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=bug-90898-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--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 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.