| Summary: | With randr-1.2 branch the XV output is only as big as the LVDS screen. | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Sjoerd Simons <sjoerd> |
| Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> |
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | medium | CC: | alexdeucher, raffaele |
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Sjoerd Simons
2007-06-05 10:09:12 UTC
the Xv code needs to be reworked to take into account the crtc sizes and some other things. It's on my todo list. actually looking at this more, I think the problem is xrandr/xserver related. If you are using clone mode, the desktop dimensions are probably clipped to the first crtc's size as it's probably the compatibility crtc. Those dimensions are what apps get when they query screen dimensions. I'm not sure how to get around that. xrandr may provide an interface so your app can get both crtc sizes, I'm just not sure off hand. Sorry for not being clear about this. It's not the case the xv window is just clipped at a certain size, but that even a windowed xv won't give any output if i drag it outside of a certain region on the screen.. (This is both in clone and non-clone mode btw) The clipping info needs to be updated depending on which crtc is being used. I'll see if I can get this fixed up in the next day or so. I experience the same here. With a fresh started system i can use XV to display films on my laptop with a screen resolution of 1400x1050 without problems. As soon i attach a 720p (1280x720) beamer im not able to resize the films beyond a with of 1280 pixels. This does not change even after i remove the beamer. The only way i figured yet to reset this is to restart the X server. Can you update and try again? I still think part of this may be app/wm related. Anyway the driver should handle it better now. Use XV_CRTC attribute: -1 auto, 0 crtc0, 1 crtc1 I tried with today's git. No changes in the behaviour unfortunately. Switching CRTC's with XV_CRT works fine though.. The problem is on the app/server side. This issue is with xinerama information and clone modes. apps query the xinerama info from the server and get the crtc dimensions of the first crtc (the laptop screen in this case). This affects other xinerama aware apps as well, not just Xv. Unfortunately, I can't think of good automatic workaround. Hmm.. But i also get this when i turn off the LVDS (using xrandr --output LVDS --off) and when using normal dual-head mode (thus not cloned mode)? I suspect the wm queries once at server start up and then sticks to that info for the life of the session. The driver side should be correct however. it might be interesting to try with twm and a bare X server or a non-xinerama aware Xv app. I tried with twm and gst-launch videotestsrc ! xvimagesink as test program.. I had a quick look at the xvimagesink code and it doesn't use xinerama. The issue stays the same though.... Fixed: 5d044b9f74c7aa7e12f2822896fed881e2ca9d19 update your driver to the version in git. (In reply to comment #12) > Fixed: > 5d044b9f74c7aa7e12f2822896fed881e2ca9d19 > update your driver to the version in git. Indeed. Thanks for your work! |
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.