Summary: | xf86-video-ati git and drm-radeon-testing git: CS checker let mplayer / vlc to fail with xv | ||
---|---|---|---|
Product: | Mesa | Reporter: | Jan Buecken <jb.faq> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | jb.faq, mike |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jan Buecken
2011-02-22 05:51:49 UTC
The commit 7ac3a2e0bcdadff7c7172a9f833f526b526da16b belongs to the xf86-video-ati git. (To make clear it does not belong to the drm-radeon-testing git branch). (In reply to comment #1) > The commit 7ac3a2e0bcdadff7c7172a9f833f526b526da16b belongs to the > xf86-video-ati git. (To make clear it does not belong to the drm-radeon-testing > git branch). I also see this bug with on my rv790 32bit build. I notice that using d-r-t from January works OK with current git ddx. Is this still an issue with the latest commits in xf86-video-ati? This is probably be related to the CS block size checking changes in d-r-t (http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=6ee3727feedf15da9c776efca3c65519cf7bb10b). Does 2.6.38-rc6 or drm-fixes work ok? (In reply to comment #3) > Is this still an issue with the latest commits in xf86-video-ati? Yes. Sorry, my git bisect log is misunderstanding: Ofcourse I tested xf86-video-ati from today, but I began with the bisect at the XV patches (I first thought they are the first failing patches, but after the problem holds without these patches, I began bisecting from the stable release). > This is > probably be related to the CS block size checking changes in d-r-t > (http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=6ee3727feedf15da9c776efca3c65519cf7bb10b). Yes. > Does 2.6.38-rc6 or drm-fixes work ok? I don't test this yet, but is it necessary? Because it is maybe more important that I just reverted (http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=6ee3727feedf15da9c776efca3c65519cf7bb10b) and testet this d-r-t. And this kernel works ok. Thus this is the failing patch at the kernel side. But which patch / branch is wrong in reality? (In reply to comment #4) > > I don't test this yet, but is it necessary? Because it is maybe more important > that I just reverted > (http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commitdiff;h=6ee3727feedf15da9c776efca3c65519cf7bb10b) > and testet this d-r-t. And this kernel works ok. Thus this is the failing patch > at the kernel side. > > But which patch / branch is wrong in reality? The d-r-t branch needs to be fixed up to not reject the linear aligned buffers from the ddx. Does this commit to the ddx fix the issue? http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=91070cfd75d5607c4a72ace780f830f0ddb40e84 (In reply to comment #6) > Does this commit to the ddx fix the issue? > http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=91070cfd75d5607c4a72ace780f830f0ddb40e84 No. can you test with latest -ati master? I've got a 1080p video playing here now. I quickly tested it before leaving the house this morning. Seems to be working, though it did look jerky Thanks, works with newest xf86-video-ati git (and d-r-t) on my rv630. Cannot confirm that it looks jerky... Greetings Jan Bücken. (In reply to comment #8) > can you test with latest -ati master? > > I've got a 1080p video playing here now. Fixed for me on rv790. Can't see any jerkyness that isn't also present with old d-r-t + ddx without the fix. AFAIK no linux player will vsync properly so nothing is ever perfect. Generally xv wait for vline is much worse than gl unless full height of the screen is used (and then it will fall apart in the case of fps = refresh unless mplayer -nodouble is used). I've also found that cpufreq on_demand does not play well with mplayer and HD. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.