Hello Dimitry,
Thanks for the patch. The BCI_LINE_MISC thing is already corrected on
the savage-1_0_0-branch. The other things look like attempts to enable
DRI on a chip for which DRI is not supported at this point. As was said
before, the S3 driver has DRI support for the Savage4 series but not the
SavageMX. When we have Savage4 working we (you?) may be able to enable
DRI on the SavageMX. But this is apperently not just a matter of
changing a few flags. I don't know how big the differences are. It was
mentioned that UtahGLX has a working SavageMX driver.
Regards,
Felix
On Fri, 26 Sep 2003 13:46:01 +0600
"Dimitry N. Naldaev" <[EMAIL PROTECTED]> wrote:
> В сообщении от 26 Сентябрь 2003 04:40 Felix Kühling
> написал:
> > On Mon, 22 Sep 2003 11:26:50 +0600
> >
> > "Dimitry N. Naldaev" <[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > > I decided to focus on 2D problem first but i don't know how I
> > > can
> > > > debug the 2D driver and found where is the problem. I would appreciate
> > > any
> > > > information or docs about debugging this kind of problem.
> > > I have fixed some problems for Xfree 4.2.0 and savage MX but there are
> > > still more :-( so I can try to help you
> >
> > Could you send a patch of the changes you made to the 2D driver?
>
> Yes I could :-)
> I try to enable DRI on Savage MX with S3 XFree86 4.2.0 3D driver
>
> After Instaling S3 driver on XFree86 4.2.0 source, I patch the source up to
> 4.2.1 because this is version of X instaled on my notebook. The patch have
> been applied cleanly and do not touch any files from S3
> After that I have done make World mainly to make Makefiles (and what are
> needded besides) But I do not Install whole new build of X instead I go in S3
> savage driver dirs and make insttall as root in them (I have made backup copy
> of /usr/X11R6/lib/modules/drivers/savage_drv.o before)
>
> This patch need to be applied in xc/programs/Xserver/hw/xfree86/drivers/savage
> directory with command patch -p1
>
> This patch solve the next problems:
>
> 1) It force enabling DRI on all Savage chips but to do this you need to define
> symbol FORCE_DRI in compile time. This can be done, for example, with command
> make EXTRA_DEFINES="-DFORCE_DRI"
> So errors
> (EE) SAVAGE(0): DRI isn't enabled
> (EE) SAVAGE(0): Direct rendering disabled
> go away from the XFee86.log
>
> 2)I fix init screen corruption on Savage MX bug when DRI forced. The problem
> was caused by the nex code which is part of
> savage_dri.c/SAVAGEDRIFinishScreenInit() function
>
> {
> unsigned int value = 0;
>
> OUTREG(0x850C,(INREG(0x850C) | 0x00008000));
>
> /* we don't use Y range flag,so comment it */
> /*
> if(pSAVAGEDRI->width <= 1024)
> value |= (1<<29);
> */
> if(pSAVAGEDRI->cpp == 2)
> {
> value |= (((pSAVAGEDRI->width + 0x3F) & 0xFFC0) >> 6) << 20;
> value |= 2<<30;
> }
> else
> {
> value |= (((pSAVAGEDRI->width + 0x1F) & 0xFFE0) >> 5) << 20;
> value |= 3<<30;
> }
>
> OUTREG(0x48C40, value|(pSAVAGEDRI->frontOffset >> 5) ); /* front */
> OUTREG(0x48C44, value|(pSAVAGEDRI->backOffset >> 5) ); /* back */
> OUTREG(0x48C48, value|(pSAVAGEDRI->depthOffset >> 5) ); /* depth */
> }
>
> Are this code needed at all ? The problem of the code is the grep 0x48C40 *.c
> in the savage 2D driver dir provide _exactly_ one match located in the above
> code and SAVAGEDRIFinishScreenInit() function is called from SavageScreenInit
> after SavageSaveRestoreState() call !!! so after VT switch ie after
> SavageLeaveVT() and SavageEnterVT() calls we restore original state of the
> registers...(Am I right or I am mistaken?) It is why VT switch fix screen
> corrution on savage MX
>
> So test my patch on oficialy DRI enebled chips please and report if it work...
>
> 3) It fix Memory manager initialization fall bug. So error
> (EE) SAVAGE(0): Memory manager initialization to (0,0) (1024,-1) failed.
> go away from the XFee86.log. The ful log is attached
> glxinfo report dri enabled see attachment
> and glxgears now do not crash Xserver but eat all processor power
> so system practicaly do not react on the keyboard and mouse button events and
> unusable :-( there is nothing appear in glxrears window. The output of
> glxgears attached. anormal high fps was when I hid the glxgears window by
> another window...
>
> whre I need to look / dig so solve this ptoblem ? I haven't any idia yet :-(
>
> 4) The patch DO NOT solve the enlightenmetn screen corruption problem I have
> reported before :-( this poblem need more investigation and can bee related
> with problem reported by Rafael. Are you using enlightenment window manager?
> or what WM you are using?
>
> > AFAICT Rafael didn't change the 2D driver yet, so your patch should
> > apply cleanly.
> My patch probably do not fix Rafael problem (BTW what video hardware you are
> using?)
>
> Now I have updated my work copy of savage-0-0-1-branch to
> savage-1_0_0-branch and notice that some files in savage catalogue are not
> changed (!) There is relevant part of cvs update report
>
> cvs server: Updating xc/programs/Xserver/hw/xfree86/drivers/savage
> P xc/programs/Xserver/hw/xfree86/drivers/savage/Imakefile
> P xc/programs/Xserver/hw/xfree86/drivers/savage/savage_accel.c
> P xc/programs/Xserver/hw/xfree86/drivers/savage/savage_bci.h
> cvs server: xc/programs/Xserver/hw/xfree86/drivers/savage/savage_common.h is
> no longer in the repository
> P xc/programs/Xserver/hw/xfree86/drivers/savage/savage_cursor.c
> P xc/programs/Xserver/hw/xfree86/drivers/savage/savage_dga.c
> U xc/programs/Xserver/hw/xfree86/drivers/savage/savage_dri.c
> U xc/programs/Xserver/hw/xfree86/drivers/savage/savage_dri.h
> U xc/programs/Xserver/hw/xfree86/drivers/savage/savage_dripriv.h
> P xc/programs/Xserver/hw/xfree86/drivers/savage/savage_driver.c
> P xc/programs/Xserver/hw/xfree86/drivers/savage/savage_driver.h
> U xc/programs/Xserver/hw/xfree86/drivers/savage/savage_drm.h
> U xc/programs/Xserver/hw/xfree86/drivers/savage/savage_hwmc.c
> P xc/programs/Xserver/hw/xfree86/drivers/savage/savage_regs.h
> U xc/programs/Xserver/hw/xfree86/drivers/savage/savage_sarea.h
> U xc/programs/Xserver/hw/xfree86/drivers/savage/savage_util.c
> U xc/programs/Xserver/hw/xfree86/drivers/savage/savage_util.h
> P xc/programs/Xserver/hw/xfree86/drivers/savage/savage_vbe.h
> P xc/programs/Xserver/hw/xfree86/drivers/savage/savage_video.c
>
> So 2D driver not the same which go from S3 and probably more correct merge is
> needed... I'll try to investigate the problem in near future...
> >
> > > > I'm using the 2D driver on savage_1-0-0_branch and i didn't
> > > > change
> > >
> > > > anything except Imakefile because it is pointing to wrong directorys.
> > >
>
> With best regards,
> Dimitry Naldaev
>
------------ __\|/__ ___ ___ -------------------------
Felix ___\_e -_/___/ __\___/ __\_____ You can do anything,
K�hling (_____\�/____/ /_____/ /________) just not everything
[EMAIL PROTECTED] \___/ \___/ U at the same time.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
