Re: [Xpert]Trident Chipsets & Xv support
Today I changed the pTrident->hsync -= 11; value. It removed the blue
line from the right side of the picture, but it still remains in the
top. Has anyone else found a better solution?
Also has anyone been able to play movies NOT fullscreen?
Thanx for all the help.
Is there a way to compile a file without compiling the whole xfree
again?
--
Regards
|Anders Rune Jensenicq : #52926571|
|Markusgade 7 4. THemail: [EMAIL PROTECTED] |
|9000 Ålborg, Denmark web : www.gnulinux.dk |
On Thu, 2001-10-11 at 22:11, John Clemens wrote:
>
> Egbert, Alan...
>
> More on this thread from the BladeXP camp..
>
> As reported earlier, here are the results I've had so far working with my
> CyberBladeXPm8 based laptop (HP N5430). All at 16bpp color bepth. Using
> mplayer -vo xv with Tom's Hardware Guide's CPU Burning avi and RealONE
> player with a DVD trailer.
>
> first, the hsync and vsync values that work for me (elimnate the "blue"
> from around the edges) are:
>
> pTrident->hsync -= 11;
> pTrident->vsync += 0;
>
> second, with the default XFree86 driver, I get video playing with the
> following display:
>
> +-+
> | Bot| Bot |
> | right | Left |
> +-+
> | Green / Garbage |
> | |
> +-+
>
> Playing with the VID_ flags mentioned earlier today effected it, but only
> made it worse. (well, VID_OFF_SHIFT_4 seems to shift the tmage just above
> the screen..? i complete guess on my part)
>
> I've traced the code down to calculating 'offset' in
> trident_cideo.c:TRIDENTDisplayVideo, notibly this piece of code:
>
> if (pTrident->Chipset >= CYBERBLADEXPm8) {
> int bpp = pScrn->bitsPerPixel >> 3;
> int dstPitch = ((width << 1) + 15) & ~15;
> offset += (((dstPitch * (height - 1)) + bpp - 1) / bpp) >> 4;
> }
>
> I'm confused as to what this code is trying to do.. but by blindly playing
> with it, i've discovered a few things:
>
> if i change the shift value to something other than 4 (i.e., 5,6,7 or 8,
> ,16, 24) in the 'offset +=' line, the image seems to get a little better
> each time, with 16 being the best.
>
> let me try illustrating what I see when the shift is set to 8:
>
> .
>
> ++--+---+
> ++ | |
> ++ R| |
> ++ I| Bottom|
> ++ G| Left |
> ++ H| |
> ++ T| |
> ++ | |
> +---+---+
> | Garbage |
> +---+
>
> by playing with the offsets, I'm able to get the image much more
> centered.. It also appears that the left/right inversion in just line wrap
> beacuse the Xv window and memory aren't quite aligned (It's as if the
> video things the real 0,0 coortinate of the windo is where the '.' is
> above the screen.)
>
> Where you see '++' on the left of the image is where
> there's a slight (maybe 2-3 pixels wide?) doubling of the left side of the
> image.. ie, the first 3 pixel's are displayed, and then displayed again in
> the next three, than the image continues normally. What could be causing
> that?
>
> Realizing that by increasing the shift i was making the value approach 0,
> I took that line out. By taking out the line completely, ie, not
> modifying the offset, the image becomes almost 100% correct. (i relized
> this as i was typing this email) I get some garbage on the bottom
> pixel-line (almost appears to be 10 pixels of grabage/10 pixels of
> video/10pixels of garbage... etc..) and I still get the "image doubling"
> on the left side. but it does work nearly perfectly.
>
> So my questions: Why was the above code put in? what is it trying to do?
> How do I get rid of the last line of garbage? Where's the doublingo n the
> left side of the image coming from?
>
> sorry for the long post.
> john.c
>
> --
> John Clemens http://www.deater.net/john
> [EMAIL PROTECTED] ICQ: 7175925, IM: PianoManO8
> "I Hate Quotes" -- Samuel L. Clemens
>
>
>
> ___
> Xpert mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xpert
>
PGP signature
Re: [Xpert]Trident Chipsets & Xv support
Anders Rune Jensen writes: > pTrident->hsync -= 11; This should really be "-= 15" 11 works for me too but when I move the video window past the borders I get some distortion. > pTrident->vsync += 0; > This value is OK. You need to look at trident_dac.c Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
On Fri, Oct 19, 2001 at 04:51:44PM +0200, Anders Rune Jensen wrote: > pTrident->hsync -= 11; > pTrident->vsync += 0; > > In which file do you change these settings, I can't find them in > trident_video.c > trident_dac.c Alan. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
pTrident->hsync -= 11;
pTrident->vsync += 0;
In which file do you change these settings, I can't find them in
trident_video.c
Thanx in advance
Anders Rune Jensen
On Thu, 2001-10-11 at 22:11, John Clemens wrote:
>
> Egbert, Alan...
>
> More on this thread from the BladeXP camp..
>
> As reported earlier, here are the results I've had so far working with my
> CyberBladeXPm8 based laptop (HP N5430). All at 16bpp color bepth. Using
> mplayer -vo xv with Tom's Hardware Guide's CPU Burning avi and RealONE
> player with a DVD trailer.
>
> first, the hsync and vsync values that work for me (elimnate the "blue"
> from around the edges) are:
>
> pTrident->hsync -= 11;
> pTrident->vsync += 0;
>
> second, with the default XFree86 driver, I get video playing with the
> following display:
>
> +-+
> | Bot| Bot |
> | right | Left |
> +-+
> | Green / Garbage |
> | |
> +-+
>
> Playing with the VID_ flags mentioned earlier today effected it, but only
> made it worse. (well, VID_OFF_SHIFT_4 seems to shift the tmage just above
> the screen..? i complete guess on my part)
>
> I've traced the code down to calculating 'offset' in
> trident_cideo.c:TRIDENTDisplayVideo, notibly this piece of code:
>
> if (pTrident->Chipset >= CYBERBLADEXPm8) {
> int bpp = pScrn->bitsPerPixel >> 3;
> int dstPitch = ((width << 1) + 15) & ~15;
> offset += (((dstPitch * (height - 1)) + bpp - 1) / bpp) >> 4;
> }
>
> I'm confused as to what this code is trying to do.. but by blindly playing
> with it, i've discovered a few things:
>
> if i change the shift value to something other than 4 (i.e., 5,6,7 or 8,
> ,16, 24) in the 'offset +=' line, the image seems to get a little better
> each time, with 16 being the best.
>
> let me try illustrating what I see when the shift is set to 8:
>
> .
>
> ++--+---+
> ++ | |
> ++ R| |
> ++ I| Bottom|
> ++ G| Left |
> ++ H| |
> ++ T| |
> ++ | |
> +---+---+
> | Garbage |
> +---+
>
> by playing with the offsets, I'm able to get the image much more
> centered.. It also appears that the left/right inversion in just line wrap
> beacuse the Xv window and memory aren't quite aligned (It's as if the
> video things the real 0,0 coortinate of the windo is where the '.' is
> above the screen.)
>
> Where you see '++' on the left of the image is where
> there's a slight (maybe 2-3 pixels wide?) doubling of the left side of the
> image.. ie, the first 3 pixel's are displayed, and then displayed again in
> the next three, than the image continues normally. What could be causing
> that?
>
> Realizing that by increasing the shift i was making the value approach 0,
> I took that line out. By taking out the line completely, ie, not
> modifying the offset, the image becomes almost 100% correct. (i relized
> this as i was typing this email) I get some garbage on the bottom
> pixel-line (almost appears to be 10 pixels of grabage/10 pixels of
> video/10pixels of garbage... etc..) and I still get the "image doubling"
> on the left side. but it does work nearly perfectly.
>
> So my questions: Why was the above code put in? what is it trying to do?
> How do I get rid of the last line of garbage? Where's the doublingo n the
> left side of the image coming from?
>
> sorry for the long post.
> john.c
>
> --
> John Clemens http://www.deater.net/john
> [EMAIL PROTECTED] ICQ: 7175925, IM: PianoManO8
> "I Hate Quotes" -- Samuel L. Clemens
>
>
>
> ___
> Xpert mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xpert
>
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
I just finished getting the cvs source and I have the exact same
problems as you, the fix you provided works almost perfect! Thank you so
much. Alan please update cvs and try to fix the garbled in the bottom of
the screen.
Im really excited Now I can use linux as my only platform on my
laptop!
Question: Has anyone been able to get tv-out working? Or have any ideas
on how to do this? Any help would be great.
System Specs:
Toshiba Tecra 8200
P3 750
Trident Cyberblade XP 16mb
On Thu, 2001-10-11 at 22:11, John Clemens wrote:
>
> Egbert, Alan...
>
> More on this thread from the BladeXP camp..
>
> As reported earlier, here are the results I've had so far working with my
> CyberBladeXPm8 based laptop (HP N5430). All at 16bpp color bepth. Using
> mplayer -vo xv with Tom's Hardware Guide's CPU Burning avi and RealONE
> player with a DVD trailer.
>
> first, the hsync and vsync values that work for me (elimnate the "blue"
> from around the edges) are:
>
> pTrident->hsync -= 11;
> pTrident->vsync += 0;
>
> second, with the default XFree86 driver, I get video playing with the
> following display:
>
> +-+
> | Bot| Bot |
> | right | Left |
> +-+
> | Green / Garbage |
> | |
> +-+
>
> Playing with the VID_ flags mentioned earlier today effected it, but only
> made it worse. (well, VID_OFF_SHIFT_4 seems to shift the tmage just above
> the screen..? i complete guess on my part)
>
> I've traced the code down to calculating 'offset' in
> trident_cideo.c:TRIDENTDisplayVideo, notibly this piece of code:
>
> if (pTrident->Chipset >= CYBERBLADEXPm8) {
> int bpp = pScrn->bitsPerPixel >> 3;
> int dstPitch = ((width << 1) + 15) & ~15;
> offset += (((dstPitch * (height - 1)) + bpp - 1) / bpp) >> 4;
> }
>
> I'm confused as to what this code is trying to do.. but by blindly playing
> with it, i've discovered a few things:
>
> if i change the shift value to something other than 4 (i.e., 5,6,7 or 8,
> ,16, 24) in the 'offset +=' line, the image seems to get a little better
> each time, with 16 being the best.
>
> let me try illustrating what I see when the shift is set to 8:
>
> .
>
> ++--+---+
> ++ | |
> ++ R| |
> ++ I| Bottom|
> ++ G| Left |
> ++ H| |
> ++ T| |
> ++ | |
> +---+---+
> | Garbage |
> +---+
>
> by playing with the offsets, I'm able to get the image much more
> centered.. It also appears that the left/right inversion in just line wrap
> beacuse the Xv window and memory aren't quite aligned (It's as if the
> video things the real 0,0 coortinate of the windo is where the '.' is
> above the screen.)
>
> Where you see '++' on the left of the image is where
> there's a slight (maybe 2-3 pixels wide?) doubling of the left side of the
> image.. ie, the first 3 pixel's are displayed, and then displayed again in
> the next three, than the image continues normally. What could be causing
> that?
>
> Realizing that by increasing the shift i was making the value approach 0,
> I took that line out. By taking out the line completely, ie, not
> modifying the offset, the image becomes almost 100% correct. (i relized
> this as i was typing this email) I get some garbage on the bottom
> pixel-line (almost appears to be 10 pixels of grabage/10 pixels of
> video/10pixels of garbage... etc..) and I still get the "image doubling"
> on the left side. but it does work nearly perfectly.
>
> So my questions: Why was the above code put in? what is it trying to do?
> How do I get rid of the last line of garbage? Where's the doublingo n the
> left side of the image coming from?
>
> sorry for the long post.
> john.c
>
> --
> John Clemens http://www.deater.net/john
> [EMAIL PROTECTED] ICQ: 7175925, IM: PianoManO8
> "I Hate Quotes" -- Samuel L. Clemens
>
>
>
> ___
> Xpert mailing list
> [EMAIL PROTECTED]
> http://XFree86.Org/mailman/listinfo/xpert
>
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
On Mon, Sep 24, 2001 at 09:46:19PM +0100, Alan Hourihane wrote: > Can I urge people with Trident chips (laptops especially) to get the > latest CVS code to test Xv support and provide some feedback. > I have a Cyberblade I1 in a Compaq Preserio 1200 laptop. With XFree 4.0.3 or 4.1.0 attempting to play a DVD with ogle resulted in a display with the left and right portions reversed and a band down the middle. (I recall earlier posts about this) I've upgraded to the latest CVS (as of a few days ago) and it's now worse than before. Nothing but bands of various colors with no resemblance to the video at all. The normal X display and desktop work fine, so does switching between consoles and X. I tried playing with the hsync/vsync values as suggested in an earlier post with no luck. Any other suggestions? Can I provide any additional info that might help? Ken -- Ken Koster, N7IPB [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
Geoffrey Hausheer writes: > > > > > Another update on My Twinhead Powerslim 600 with the Cyber9525DVD: > > > > I changed the hsync hardcoded adjustment to 0 (it was initally 23) > > > > I left the vsync at -2. > > > > > > This will break it for others. We still don't know exactly how to > > > calculate these values exactly. > > > > I've done some playing around with my laptop based on a Trident > > Cyber9525DVD, and I'm beginning to believe that the CRTC values can't be > > correct. In particular, the CRTC values change from what X sets when I > > press Fn-F5 to switch displays, and when I plug these values into the LCD[] > > array, the overlay becomes centered properly (without modifying the > > h/vsync). > > Thanks for figuring this out! Now that I know what's causing the Xvideo offset > to re-occur, I can switch to console and back to restore it to being 'centered'. > Sure it's not a perfect fix, but I expect y'all will figure that out before the > next major release :) If there's anything I can do to help, please let me know. > First of all: The CRTC values we set _are_ correct. They work for a wide range of displays. The values I have commented out came from my test system but they caused problems on several boxes. They may not be the same your system sets up - that doesn't matter as long as they work. I still have no clear idea how the offset registers need to be caluculated. The documentation says to use the number pixel clocks (lines in case of the vertical offset) between the rising edge of the h/vsync and the begin of the video frame. If we do that we need to add an offset which has been obtained empirically. For some reason this offset differs from chipset to chipset (or even from system to system). If the CRTC values set by the BIOS cause the video to be displayed correctly it would be interesting to know which values exactly make the difference. Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
> > > Another update on My Twinhead Powerslim 600 with the Cyber9525DVD: > > > I changed the hsync hardcoded adjustment to 0 (it was initally 23) > > > I left the vsync at -2. > > > > This will break it for others. We still don't know exactly how to > > calculate these values exactly. > > I've done some playing around with my laptop based on a Trident > Cyber9525DVD, and I'm beginning to believe that the CRTC values can't be > correct. In particular, the CRTC values change from what X sets when I > press Fn-F5 to switch displays, and when I plug these values into the LCD[] > array, the overlay becomes centered properly (without modifying the > h/vsync). Thanks for figuring this out! Now that I know what's causing the Xvideo offset to re-occur, I can switch to console and back to restore it to being 'centered'. Sure it's not a perfect fix, but I expect y'all will figure that out before the next major release :) If there's anything I can do to help, please let me know. Thanks again, .Geoff - Protect yourself from spam, use http://sneakemail.com ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
On Thu, 4 Oct 2001, Egbert Eich wrote: > Alan Hourihane writes: > > > > > Egbert - I hope we really don't have to kludge around like this, but if we > > do, you can check the current video output mode in the BlockHandler and > > I just did. Had a brown paper bag ready - just in case. > > > use a callback to update values. > > > > I did some code which does it every 100 frames. This seems to be very > reasonable. But I'll play around a little bit more. BlockHandler is > a nice idea, too. > The BlockHandler will get called once per frame. Reading a register every frame is not a big deal. The overhead of that is small compared to copying all that data across the bus. Alot of drivers have to read every frame. MGA and ATI both do. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
Alan Hourihane writes: > > > Egbert - I hope we really don't have to kludge around like this, but if we > do, you can check the current video output mode in the BlockHandler and I just did. Had a brown paper bag ready - just in case. > use a callback to update values. > I did some code which does it every 100 frames. This seems to be very reasonable. But I'll play around a little bit more. BlockHandler is a nice idea, too. Cheers, Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
Around 16 o'clock on Oct 4, Alan Hourihane wrote: > > I agree, hotkey display switching will most likely mess up the > > video offsets. The Xserver doesn't get notified when a switch happens > > therefore we cannot adapt our values. I don't like to read back the > > CRTC registers on every frame to see if they have changed. > > Maybe I can add some code to do this every 100 or so frames. > > > Egbert - I hope we really don't have to kludge around like this, but if we > do, you can check the current video output mode in the BlockHandler and > use a callback to update values. You might as well do it every time you put a frame on the screen; that only happens every 33ms. I think you can afford a few PCI read cycles at that rate. [EMAIL PROTECTED]XFree86 Core Team SuSE, Inc. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
On Thu, Oct 04, 2001 at 05:56:42PM +0200, Egbert Eich wrote: > Chad Kitching writes: > > > > Another update on My Twinhead Powerslim 600 with the Cyber9525DVD: > > > > I changed the hsync hardcoded adjustment to 0 (it was initally 23) > > > > I left the vsync at -2. > > > > > > This will break it for others. We still don't know exactly how to > > > calculate these values exactly. > > > > I've done some playing around with my laptop based on a Trident > > Cyber9525DVD, and I'm beginning to believe that the CRTC values can't be > > correct. In particular, the CRTC values change from what X sets when I > > press Fn-F5 to switch displays, and when I plug these values into the LCD[] > > array, the overlay becomes centered properly (without modifying the > > h/vsync). I haven't managed to get 640x480 (unstretched) to work with the > > overlay, since I can't get the trident driver to set the "proper" values > > (e.g. the values I set in the LCD array end up being different from what > > gets programmed into the VGA CRTC registers). > > > > The CRTC values I'm getting from my card when I switch video outputs is the > > same ones that are '#if 0'ed out above the current LCD[] array. > > > > > > The current code doesn't take the horizontal sync skew (CRTC[5]5:6) > into account. This might have caused this problem. > I fixed this. Now we may have to retune the video skews. > > I agree, hotkey display switching will most likely mess up the > video offsets. The Xserver doesn't get notified when a switch happens > therefore we cannot adapt our values. I don't like to read back the > CRTC registers on every frame to see if they have changed. > Maybe I can add some code to do this every 100 or so frames. > Egbert - I hope we really don't have to kludge around like this, but if we do, you can check the current video output mode in the BlockHandler and use a callback to update values. Alan. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
Chad Kitching writes: > > > Another update on My Twinhead Powerslim 600 with the Cyber9525DVD: > > > I changed the hsync hardcoded adjustment to 0 (it was initally 23) > > > I left the vsync at -2. > > > > This will break it for others. We still don't know exactly how to > > calculate these values exactly. > > I've done some playing around with my laptop based on a Trident > Cyber9525DVD, and I'm beginning to believe that the CRTC values can't be > correct. In particular, the CRTC values change from what X sets when I > press Fn-F5 to switch displays, and when I plug these values into the LCD[] > array, the overlay becomes centered properly (without modifying the > h/vsync). I haven't managed to get 640x480 (unstretched) to work with the > overlay, since I can't get the trident driver to set the "proper" values > (e.g. the values I set in the LCD array end up being different from what > gets programmed into the VGA CRTC registers). > > The CRTC values I'm getting from my card when I switch video outputs is the > same ones that are '#if 0'ed out above the current LCD[] array. > > The current code doesn't take the horizontal sync skew (CRTC[5]5:6) into account. This might have caused this problem. I fixed this. Now we may have to retune the video skews. I agree, hotkey display switching will most likely mess up the video offsets. The Xserver doesn't get notified when a switch happens therefore we cannot adapt our values. I don't like to read back the CRTC registers on every frame to see if they have changed. Maybe I can add some code to do this every 100 or so frames. Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
Has anyone been able to enable tv-out? Plz post links etc. I've tried to find out as much as I can, but I seem to end in something like: 3dfx uses lm_sensors to enable tvou. S3 uses a speciel program and others just unplug their monitor (a little hard on a laptop :(). Any ideas on how to do it on a laptop with a trident Cyberblade XP? On ons, 2001-09-26 at 02:06, Chad Kitching wrote: > Okay, I think there's still a small problem with the fix for the Xv overlay. > Attached is a diff that fixes it on my laptop. I haven't yet got around to > playing with the h/v offsets, but unfortunately, they vary with each display > mode on my laptop (and changes when I modify the output device). > > From: "Alan Hourihane" <[EMAIL PROTECTED]> > > Can I urge people with Trident chips (laptops especially) to get the > > latest CVS code to test Xv support and provide some feedback. > -- Med venlig Hilsen |Anders Rune Jensenicq : #52926571| |Markusgade 7 4. THemail: [EMAIL PROTECTED] | |9000 Ålborg web : www.gnulinux.dk | PGP signature
Re: [Xpert]Trident Chipsets & Xv support
> > Another update on My Twinhead Powerslim 600 with the Cyber9525DVD: > > I changed the hsync hardcoded adjustment to 0 (it was initally 23) > > I left the vsync at -2. > > This will break it for others. We still don't know exactly how to > calculate these values exactly. I've done some playing around with my laptop based on a Trident Cyber9525DVD, and I'm beginning to believe that the CRTC values can't be correct. In particular, the CRTC values change from what X sets when I press Fn-F5 to switch displays, and when I plug these values into the LCD[] array, the overlay becomes centered properly (without modifying the h/vsync). I haven't managed to get 640x480 (unstretched) to work with the overlay, since I can't get the trident driver to set the "proper" values (e.g. the values I set in the LCD array end up being different from what gets programmed into the VGA CRTC registers). The CRTC values I'm getting from my card when I switch video outputs is the same ones that are '#if 0'ed out above the current LCD[] array. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]Trident Chipsets & Xv support
Geoffrey Hausheer writes: > On Mon, Sep 24, 2001 at 09:46:19PM +0100, Alan Hourihane wrote: > > Can I urge people with Trident chips (laptops especially) to get the > > latest CVS code to test Xv support and provide some feedback. > > Another update on My Twinhead Powerslim 600 with the Cyber9525DVD: > I changed the hsync hardcoded adjustment to 0 (it was initally 23) > I left the vsync at -2. This will break it for others. We still don't know exactly how to calculate these values exactly. Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]Trident Chipsets & Xv support
On Mon, Sep 24, 2001 at 09:46:19PM +0100, Alan Hourihane wrote: > Can I urge people with Trident chips (laptops especially) to get the > latest CVS code to test Xv support and provide some feedback. Another update on My Twinhead Powerslim 600 with the Cyber9525DVD: I changed the hsync hardcoded adjustment to 0 (it was initally 23) I left the vsync at -2. This makes the dispaly perfectly centered with the XVideo stuff. However, after some amount of time, when I go back into XVideo, I get about 7 pixels of blue on the right side, and one on the bottom. Restarting X brings it back to being cenetered again. Otherwise, these settings work perfectly for this laptop. Thanks, .Geoff - Protect yourself from spam, use http://sneakemail.com ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
Thanks Chad, Missed that. Applied your fix. Alan. On Tue, Sep 25, 2001 at 07:06:13PM -0500, Chad Kitching wrote: > Okay, I think there's still a small problem with the fix for the Xv overlay. > Attached is a diff that fixes it on my laptop. I haven't yet got around to > playing with the h/v offsets, but unfortunately, they vary with each display > mode on my laptop (and changes when I modify the output device). > > From: "Alan Hourihane" <[EMAIL PROTECTED]> > > Can I urge people with Trident chips (laptops especially) to get the > > latest CVS code to test Xv support and provide some feedback. > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
Okay, I think there's still a small problem with the fix for the Xv overlay. Attached is a diff that fixes it on my laptop. I haven't yet got around to playing with the h/v offsets, but unfortunately, they vary with each display mode on my laptop (and changes when I modify the output device). From: "Alan Hourihane" <[EMAIL PROTECTED]> > Can I urge people with Trident chips (laptops especially) to get the > latest CVS code to test Xv support and provide some feedback. trident_video.diff
Re: [Xpert]Trident Chipsets & Xv support
On Mon, Sep 24, 2001 at 09:46:19PM +0100, Alan Hourihane wrote: > Can I urge people with Trident chips (laptops especially) to get the > latest CVS code to test Xv support and provide some feedback. My chipset is a Cyber 9397DVD (rev f3). Latest CVS source works fine for me. XVideo is centered in the window, and is robust to console switching and to APM suspend/resume. BTW, you still can grab daily XFree86 HEAD RPMS at ftp://fr2.rpmfind.net/linux/local/SRPMS ftp://fr2.rpmfind.net/linux/local/RPMS/i386 -- fabrice ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
Well the list is called xpert for a reason. How about checking http://www.xfree86.org/cvs on how to get it first. But if you don't want to damage your Debian install I suggest you make up another partition and install a development system. Alan. On Tue, Sep 25, 2001 at 05:24:38AM +0200, Anders Rune Jensen wrote: > Yeah NO PROBLEM!! > > But how do we do that, I have xfree installed from debian packages. Can > I just remove that one and then download the cvs version and install > that one? > > On Mon, 2001-09-24 at 22:46, Alan Hourihane wrote: > > > Can I urge people with Trident chips (laptops especially) to get the > > latest CVS code to test Xv support and provide some feedback. > > > > If people can look closely at trident_dac.c for the pTrident->hsync/vsync > > values and adjust accordingly for their setup and send some comments > > regarding what you had to do to get the video centered in the video window. > > > > Thanks. > > > > Alan. > > ___ > > Xpert mailing list > > [EMAIL PROTECTED] > > http://XFree86.Org/mailman/listinfo/xpert > > > > Med venlig Hilsen: > >- > > Anders Rune Jensen > icq > : 52926571 > > Markusgade 7 4. TH > email > : [EMAIL PROTECTED] > > 9000 Ålborg > web > : http://www.gnulinux.dk > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Trident Chipsets & Xv support
Yeah NO PROBLEM!! But how do we do that, I have xfree installed from debian packages. Can I just remove that one and then download the cvs version and install that one? On Mon, 2001-09-24 at 22:46, Alan Hourihane wrote:> Can I urge people with Trident chips (laptops especially) to get the > latest CVS code to test Xv support and provide some feedback. > > If people can look closely at trident_dac.c for the pTrident->hsync/vsync > values and adjust accordingly for their setup and send some comments > regarding what you had to do to get the video centered in the video window. > > Thanks. > > Alan. > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert > Med venlig Hilsen: - Anders Rune Jensen icq : 52926571 Markusgade 7 4. TH email : [EMAIL PROTECTED] 9000 Ålborg web : http://www.gnulinux.dk PGP signature
[Xpert]Trident Chipsets & Xv support
Can I urge people with Trident chips (laptops especially) to get the latest CVS code to test Xv support and provide some feedback. If people can look closely at trident_dac.c for the pTrident->hsync/vsync values and adjust accordingly for their setup and send some comments regarding what you had to do to get the video centered in the video window. Thanks. Alan. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
