From: Sedat Dilek <sedat.dilek@googlemail.com>
To: DRI <dri-devel@lists.freedesktop.org>
Cc: daniel.vetter@ffwll.ch
Subject: Re: [PATCH 0/3] embed drm_gem_object into radeon_bo
Date: Mon, 15 Nov 2010 11:20:28 +0100 [thread overview]
Message-ID: <AANLkTimA5ex5bOirmKGZ2jC4u_YT+RVAa7R9G89XyrG3@mail.gmail.com> (raw)
Hi Daniel,
I have tried this patchset on a RV250 with linux-next (next-20101115)
in combination w/ patchset from "[PATCH 0/9] make struct drm_mm_node
embeddable" [1].
glxgears works nice.
2nd test-case is Eric Anholt's OpenArena benchmark.
The screen gets blank and system is unusable (cold start, poweroff-button).
Mesa is from master GIT branch:
$ cd ~/src/mesa
$ grep -A4 "git log" mesa.log
+ git log --pretty=short -1
commit 9cf25b3d1cd2910ae33e1faafa04629638bff0fe
Author: Marek Olšák <maraeo@gmail.com>
r300g: return shader caps from Draw for SWTCL vertex shaders
Daniel requested me to bisect:
bad: 3-3-drm-radeon-kill-radeon_bo--gobj-pointer.patch +
2-3-drm-radeon-introduce-gem_to_radeon_bo-helper.patch
good: 1-3-drm-radeon-embed-struct-drm_gem_object.patch
$cd ~/src/linux-2.6/linux-2.6.37-rc1/debian/build/source_i386_none
$ cat .pc/applied-patches
danvet-embed-drm_gem_object-into-radeon_bo/1-3-drm-radeon-embed-struct-drm_gem_object.patch
Looks like patch #2 is culprit according to Daniel.
Kind Regards,
- Sedat -
[1] http://lists.freedesktop.org/archives/dri-devel/2010-November/005420.html
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2010-11-15 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 10:20 Sedat Dilek [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-28 0:29 [PATCH 0/3] embed drm_gem_object into radeon_bo Sedat Dilek
2010-11-27 9:47 Daniel Vetter
2010-11-16 17:05 Sedat Dilek
2010-11-16 17:30 ` Daniel Vetter
2010-11-16 19:37 ` Sedat Dilek
2010-11-16 19:54 ` Sedat Dilek
2010-11-13 20:57 Daniel Vetter
2010-11-15 7:25 ` Thomas Hellstrom
2010-11-15 18:45 ` Daniel Vetter
2010-11-15 20:48 ` Thomas Hellstrom
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=AANLkTimA5ex5bOirmKGZ2jC4u_YT+RVAa7R9G89XyrG3@mail.gmail.com \
--to=sedat.dilek@googlemail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=sedat.dilek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).