[Dri-users] Re: savage driver prevents video

[John H. <mrm...@my...>]

i'd like to test this.  how do you change it to X11 system wide, or what programs support changing it?









 --- On Fri 03/19, Alex Deucher < ag...@ya... > wrote:

From: Alex Deucher [mailto: ag...@ya...]

To: mrm...@my..., fx...@gm...

     Cc: ag...@ya..., dri...@li...

Date: Fri, 19 Mar 2004 06:26:14 -0800 (PST)

Subject: Re: savage driver prevents video



<br>--- "John H." <mrm...@my...> wrote:<br>> <br>> i thought it did, but apparently not:(<br>> <br>> it does work with vesa fine, though?<br>> <br>> <br><br>like a said earlier, vesa does not have a video overlay so it is just<br>displaying the video with xputimage or xshmputimage.  You can simulate<br>the same thing on savage by choosing the X11 output plugin rather than<br>the Xv one in your video app.<br><br>What might be interesting though is that Xv may be subtlely different<br>on prosavages vs. savage4.  I noticed that tim's drivers sets a few<br>bits differently then s3's.  S3's driver never worked particularly well<br>on my savage4, but tim's is flawless.  When I ported the code, I tried<br>setting the bits as S3 had done, but it broke xv on my savage4. <br>perhaps prosavage is another story, however, Felix and other prosavage<br>users haven't had a problem so I assumed the current state was correct.<br><br>FWIW, I cleaned up the non-Xv streams code to make sure it was properly<br>enabled, but it didn't seem to make a difference (performance or<br>otherwise) so I never committed it.<br><br>Alex<br><br>> <br>> <br>>  --- On Fri 03/19, Felix =?ISO-8859-1?Q?K=FChling?= < fx...@gm...<br>> > wrote:<br>> From: Felix =?ISO-8859-1?Q?K=FChling?= [mailto: fx...@gm...]<br>> To: mrm...@my...<br>>      Cc: ag...@ya..., dri...@li...<br>> Date: Fri, 19 Mar 2004 11:40:03 +0100<br>> Subject: Re: savage driver prevents video<br>> <br>> On Fri, 19 Mar 2004 03:02:55 -0500 (EST)<br>"John H."<br>> <mrm...@my...> wrote:<br><br>> <br>> ok, this is bizarre.  I<br>> reinstalled fedora core's XFree86-4.3.0 rpm, and start X with<br>> standardsavage driver, and I get the exact same problem with<br>> video!<br><br>Did this ever work with stock XFree86. If yes, try a<br>> cold reboot. Maybe<br>there are some settings in the graphics chip's<br>> registers that are<br>screwed up by the DRI driver and not<br>> initialized to sane values by the<br>stock XFree86<br>> driver.<br><br>Felix<br><br>> <br>[snip]<br><br>><br><br>__________________________________<br>Do you Yahoo!?<br>Yahoo! Mail - More reliable, more storage, less spam<br>http://mail.yahoo.com<br>

_______________________________________________
No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com