From: "Marius Gröger" <marius.groeger@googlemail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: "Michel Dänzer" <michel@daenzer.net>, dri-devel@lists.freedesktop.org
Subject: Re: Glitch in newer drm-next/drm-radeon-testing
Date: Sun, 06 Jun 2010 19:52:33 +0200 [thread overview]
Message-ID: <4C0BE061.9010608@googlemail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1006061745250.1320@casper.infradead.org>
Am 06.06.2010 18:47, schrieb James Simmons:
>
>>> Apologies for such an unspecific description, and for what almost seems
>>> like a support request for MythTV. I wouldn't post here if I were not
>>> 100% sure it must be related with the recent drm changes.
>>
>> Note that the DRM APIs are intended for use by userspace components of
>> graphics drivers / API libraries, not applications directly. MythTV
>> shouldn't use the DRM directly for synchronization but rather use GLX
>> synchronization APIs.
>
> Tho not the case for MythTV on a embedded device requiring apps to use GLX
> wuld be to heavy. I would agree libdrm should be used.
I have found the cause for the glitch and just filed
http://bugs.freedesktop.org/show_bug.cgi?id=28411.
Regards
Marius
next prev parent reply other threads:[~2010-06-06 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 6:07 Glitch in newer drm-next/drm-radeon-testing Marius Gröger
2010-06-02 8:21 ` Michel Dänzer
2010-06-02 8:47 ` Marius Gröger
2010-06-04 13:35 ` Marius Gröger
2010-06-04 15:01 ` Alex Deucher
2010-06-04 15:10 ` Marius Gröger
2010-06-04 15:17 ` Alex Deucher
2010-06-04 18:55 ` Marius Gröger
2010-06-04 20:02 ` Alex Deucher
2010-06-06 9:17 ` Marius Gröger
2010-06-06 16:47 ` James Simmons
2010-06-06 17:52 ` Marius Gröger [this message]
2010-06-06 22:15 ` Dave Airlie
2010-08-02 10:12 ` Marius Gröger
2010-08-02 10:17 ` Dave Airlie
-- strict thread matches above, loose matches on Subject: below --
2010-06-02 6:02 Marius Gröger
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=4C0BE061.9010608@googlemail.com \
--to=marius.groeger@googlemail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsimmons@infradead.org \
--cc=michel@daenzer.net \
/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.