Re: [Dri-devel] install.sh bug
Am Dienstag, 8. Oktober 2002 00:01 schrieb Dieter Nützel: > Am Montag, 7. Oktober 2002 21:28 schrieb Linus Torvalds: > > On Mon, 7 Oct 2002, Dieter Nützel wrote: > > > The DRM files need some fixing for 2.5.40+ to compile it from DRI CVS. > > > > Note that the 2.5.x kernel is actually mostly tracking the DRI CVS tree, > > with merges every other week or so. The last merge is actually in 2.5.41, > > so the kernel tree is actually up-to-date as of Oct 2nd right now. > > Ah, some "new" IRQ stuff missing, then. > > > Right now I'm tracking it myself - which means that it is a bit erratic, > > especially as I only care about ATI cards - and if anybody wants to make > > that more timely, feel free to just send me patches. > > GREAT to hear! > > Send me your stuff ;-) > > Can't wait for the 2.5.41. Ups, 2.5.41 is currently out... Thanks, Dieter --- 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
Re: [Dri-devel] install.sh bug
Am Montag, 7. Oktober 2002 21:28 schrieb Linus Torvalds: > On Mon, 7 Oct 2002, Dieter Nützel wrote: > > The DRM files need some fixing for 2.5.40+ to compile it from DRI CVS. > > Note that the 2.5.x kernel is actually mostly tracking the DRI CVS tree, > with merges every other week or so. The last merge is actually in 2.5.41, > so the kernel tree is actually up-to-date as of Oct 2nd right now. Ah, some "new" IRQ stuff missing, then. > Right now I'm tracking it myself - which means that it is a bit erratic, > especially as I only care about ATI cards - and if anybody wants to make > that more timely, feel free to just send me patches. GREAT to hear! Send me your stuff ;-) Can't wait for the 2.5.41. Thanks, Dieter --- 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
Re: [Dri-devel] install.sh bug
On Mon, 7 Oct 2002, Dieter Nützel wrote: > > The DRM files need some fixing for 2.5.40+ to compile it from DRI CVS. Note that the 2.5.x kernel is actually mostly tracking the DRI CVS tree, with merges every other week or so. The last merge is actually in 2.5.41, so the kernel tree is actually up-to-date as of Oct 2nd right now. Right now I'm tracking it myself - which means that it is a bit erratic, especially as I only care about ATI cards - and if anybody wants to make that more timely, feel free to just send me patches. Linus --- 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
Re: [Dri-devel] install.sh bug
Am Montag, 7. Oktober 2002 20:44 schrieb Jens Owen: > Dieter Nützel wrote: > > Am Montag, 7. Oktober 2002 17:55 schrieb Jens Owen: > >>José Fonseca wrote: > >>>Next snapshots (which are now fully automated again) have this already. > >>>Notify if you run into problems. > >> > >>Jose, or anybody interested in creating an 830/845 package? TG has > >>released many bug fixes for this chipset, but we've been too busy to > >>update the package script. > > > > Is your new stuff 2.5.40+ save? > > safe? Yes, wrong term on my side ;-) > > The DRM files need some fixing for 2.5.40+ to compile it from DRI CVS. > > I wouldn't guess this is *not* related to the actual packaging scripts > (topic of this thread). OK. > Can you give a summary of the issues you see when compiling with 2.5.40+? See my post under subject: r200: UT and Q3A Intro (Cinematics) stuttering SOLVED > BTW, for anyone trying to use the 830/845 driver, I would recommend 2.4.19. For speed (mouse, keyboard, swap, disk IO behavior)? ;-) Greetings, Dieter BTW DRM needs some (more) pre-emption points for latency. -- Dieter Nützel Graduate Student, Computer Science University of Hamburg Department of Computer Science @home: Dieter.Nuetzel at hamburg.de (replace at with @) --- 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
Re: [Dri-devel] install.sh bug
Dieter Nützel wrote: > Am Montag, 7. Oktober 2002 17:55 schrieb Jens Owen: > >>José Fonseca wrote: >> >>>Next snapshots (which are now fully automated again) have this already. >>>Notify if you run into problems. >> >>Jose, or anybody interested in creating an 830/845 package? TG has >>released many bug fixes for this chipset, but we've been too busy to >>update the package script. > > > Is your new stuff 2.5.40+ save? safe? > The DRM files need some fixing for 2.5.40+ to compile it from DRI CVS. I wouldn't guess this is *not* related to the actual packaging scripts (topic of this thread). Can you give a summary of the issues you see when compiling with 2.5.40+? BTW, for anyone trying to use the 830/845 driver, I would recommend 2.4.19. -- /\ Jens Owen/ \/\ _ [EMAIL PROTECTED] /\ \ \ Steamboat Springs, Colorado --- 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
Re: [Dri-devel] install.sh bug
Am Montag, 7. Oktober 2002 17:55 schrieb Jens Owen: > José Fonseca wrote: > > Next snapshots (which are now fully automated again) have this already. > > Notify if you run into problems. > > Jose, or anybody interested in creating an 830/845 package? TG has > released many bug fixes for this chipset, but we've been too busy to > update the package script. Is your new stuff 2.5.40+ save? The DRM files need some fixing for 2.5.40+ to compile it from DRI CVS. -Dieter --- 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
Re: [Dri-devel] install.sh bug
Jens, On Mon, Oct 07, 2002 at 09:55:10AM -0600, Jens Owen wrote: >José Fonseca wrote: > >>Next snapshots (which are now fully automated again) have this already. >>Notify if you run into problems. > >Jose, or anybody interested in creating an 830/845 package? TG has >released many bug fixes for this chipset, but we've been too busy to >update the package script. > >The 2D driver is shared with the i810, however a unique DRM driver and >3D driver is required. All aspects of 830/845 support should be >building and running from the trunk, we're only missing the packaging >for binary snapshots. > >TG is not dependent on a package, but I have seen a few posts from DRI >and Xpert users who would have liked binary snapshots. No problem, I can do it. In fact I just didn't doit because I wasn't aware of the state of the driver as not much discussion about it has been going through dri-devel. I'll announce on the mailing-lists as soon as it's done. Jose Fonseca --- 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
Re: [Dri-devel] install.sh bug
José Fonseca wrote: > Next snapshots (which are now fully automated again) have this already. > Notify if you run into problems. Jose, or anybody interested in creating an 830/845 package? TG has released many bug fixes for this chipset, but we've been too busy to update the package script. The 2D driver is shared with the i810, however a unique DRM driver and 3D driver is required. All aspects of 830/845 support should be building and running from the trunk, we're only missing the packaging for binary snapshots. TG is not dependent on a package, but I have seen a few posts from DRI and Xpert users who would have liked binary snapshots. Regards, Jens -- /\ Jens Owen/ \/\ _ [EMAIL PROTECTED] /\ \ \ Steamboat Springs, Colorado --- 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
Re: [Dri-devel] install.sh bug
On Tue, Sep 24, 2002 at 02:38:51PM +0100, José Fonseca wrote: >On Sat, Aug 31, 2002 at 09:01:16AM -0600, Jens Owen wrote: >> It looks like there is some type of problem when the GL subdirectory is >> empty. Here's what the script tries to do when it get's to an empty GL >> portion of the install. >> > >Ok. The problem is at: > > echo -n " GL & GLU libraries..." > cd GL > for FILE in * > do > mv -f $XF86_GL_DIR/$FILE $XF86_GL_DIR/dri-old.$FILE >& $LOGFILE_TMP; > cp -f $FILE $XF86_GL_DIR > done > >The '*' wildcard isn't matched so it's copied verbatim into $FILE actually doing > > mv -f $XF86_GL_DIR/* $XF86_GL_DIR/dri-old.* >& $LOGFILE_TMP; > >Since I don't want to replace a bug for another, what should be the best thing to do >in >these cases? The alternatives I see are > - replacing the * for `ls` > - replacing the * for `find` > >Are there any caveats with any of these, or is there another way to do this? > [...] I took Ian Romanick's suggestion and changed all to ls -1 * | while read FILE Next snapshots (which are now fully automated again) have this already. Notify if you run into problems. José Fonseca --- 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
Re: [Dri-devel] install.sh bug
On Sat, Aug 31, 2002 at 09:01:16AM -0600, Jens Owen wrote: > It looks like there is some type of problem when the GL subdirectory is > empty. Here's what the script tries to do when it get's to an empty GL > portion of the install. > Ok. The problem is at: echo -n " GL & GLU libraries..." cd GL for FILE in * do mv -f $XF86_GL_DIR/$FILE $XF86_GL_DIR/dri-old.$FILE >& $LOGFILE_TMP; cp -f $FILE $XF86_GL_DIR done The '*' wildcard isn't matched so it's copied verbatim into $FILE actually doing mv -f $XF86_GL_DIR/* $XF86_GL_DIR/dri-old.* >& $LOGFILE_TMP; Since I don't want to replace a bug for another, what should be the best thing to do in these cases? The alternatives I see are - replacing the * for `ls` - replacing the * for `find` Are there any caveats with any of these, or is there another way to do this? Jose Fonseca > + echo -n ' GL & GLU libraries...' > + cd GL > + mv -f /usr/X11R6/lib/libdps.a /usr/X11R6/lib/libdps.so /usr/X11R6/lib/libdps.so.1 >/usr/X11R6/lib/libdps.so.1.0 /usr/X11R6/lib/libdpstk.a /usr/X11R6/lib/libdpstk.so >/usr/X11R6/lib/libdpstk.so.1 /usr/X11R6/lib/libdpstk.so.1.0 >/usr/X11R6/lib/libfntstubs.a /usr/X11R6/lib/libfontenc.a /usr/X11R6/lib/libFS.a >/usr/X11R6/lib/libGL.a /usr/X11R6/lib/libGL.so /usr/X11R6/lib/libGL.so.1 >/usr/X11R6/lib/libGL.so.1.2 /usr/X11R6/lib/libGLU.a /usr/X11R6/lib/libGLU.so >/usr/X11R6/lib/libGLU.so.1 /usr/X11R6/lib/libGLU.so.1.3 /usr/X11R6/lib/libGLw.a >/usr/X11R6/lib/libI810XvMC.a /usr/X11R6/lib/libICE.a /usr/X11R6/lib/libICE.so >/usr/X11R6/lib/libICE.so.6 /usr/X11R6/lib/libICE.so.6.3 /usr/X11R6/lib/libMagick.a >/usr/X11R6/lib/libMagick++.a /usr/X11R6/lib/libMagick.la >/usr/X11R6/lib/libMagick++.la /usr/X11R6/lib/libMagick.so >/usr/X11R6/lib/libMagick++.so /usr/X11R6/lib/libMagick.so.5 >/usr/X11R6/lib/libMagick++.so.5 /usr/X11R6/lib/libMagick.so.5.0.43 >/usr/X11R6/lib/libMagick++.so.5.0.43 /usr/X11R6/lib/libMrm.a /usr/X11R6/lib/libMrm.so >/usr/X11R6/lib/libMrm.so.1 /usr/X11R6/lib/libMrm.so.1.0.2 /usr/X11R6/lib/libMrm.so.3 >/usr/X11R6/lib/libMrm.so.3.0.1 /usr/X11R6/lib/liboldX.a /usr/X11R6/lib/libOSMesa.a >/usr/X11R6/lib/libOSMesa.so /usr/X11R6/lib/libOSMesa.so.3 >/usr/X11R6/lib/libOSMesa.so.3.3 /usr/X11R6/lib/libpsres.a /usr/X11R6/lib/libpsres.so >/usr/X11R6/lib/libpsres.so.1 /usr/X11R6/lib/libpsres.so.1.0 /usr/X11R6/lib/libSM.a >/usr/X11R6/lib/libSM.so /usr/X11R6/lib/libSM.so.6 /usr/X11R6/lib/libSM.so.6.0 >/usr/X11R6/lib/libUil.a /usr/X11R6/lib/libUil.so /usr/X11R6/lib/libUil.so.1 >/usr/X11R6/lib/libUil.so.1.0.2 /usr/X11R6/lib/libUil.so.3 >/usr/X11R6/lib/libUil.so.3.0.1 /usr/X11R6/lib/libX11.a /usr/X11R6/lib/libX11.so >/usr/X11R6/lib/libX11.so.6 /usr/X11R6/lib/libX11.so.6.2 /usr/X11R6/lib/libXau.a >/usr/X11R6/lib/libXaw3d.a /usr/X11R6/lib/libXaw3d.so /usr/X11R6/lib/libXaw3d.so.6 >/usr/X11R6/lib/libXaw3d.so.6.1 /usr/X11R6/lib/libXaw3d.so.7 >/usr/X11R6/lib/libXaw3d.so.7.0 /usr/X11R6/lib/libXaw.a /usr/X11R6/lib/libXaw.so >/usr/X11R6/lib/libXaw.so.6 /usr/X11R6/lib/libXaw.so.6.1 /usr/X11R6/lib/libXaw.so.7 >/usr/X11R6/lib/libXaw.so.7.0 /usr/X11R6/lib/libXdmcp.a /usr/X11R6/lib/libXext.a >/usr/X11R6/lib/libXext.so /usr/X11R6/lib/libXext.so.6 /usr/X11R6/lib/libXext.so.6.4 >/usr/X11R6/lib/libxf86config.a /usr/X11R6/lib/libXfont.a >/usr/X11R6/lib/libXfontcache.a /usr/X11R6/lib/libXfont.so >/usr/X11R6/lib/libXfont.so.1 /usr/X11R6/lib/libXfont.so.1.4 /usr/X11R6/lib/libXft.a >/usr/X11R6/lib/libXft.so /usr/X11R6/lib/libXft.so.1 /usr/X11R6/lib/libXft.so.1.1 >/usr/X11R6/lib/libXi.a /usr/X11R6/lib/libXinerama.a /usr/X11R6/lib/libXi.so >/usr/X11R6/lib/libXi.so.6 /usr/X11R6/lib/libXi.so.6.0 /usr/X11R6/lib/libxkbfile.a >/usr/X11R6/lib/libxkbui.a /usr/X11R6/lib/libXm.a /usr/X11R6/lib/libXm.so >/usr/X11R6/lib/libXm.so.1 /usr/X11R6/lib/libXm.so.1.0.2 /usr/X11R6/lib/libXm.so.3 >/usr/X11R6/lib/libXm.so.3.0.1 /usr/X11R6/lib/libXmu.a /usr/X11R6/lib/libXmu.so >/usr/X11R6/lib/libXmu.so.6 /usr/X11R6/lib/libXmu.so.6.2 /usr/X11R6/lib/libXmuu.a >/usr/X11R6/lib/libXmuu.so /usr/X11R6/lib/libXmuu.so.1 /usr/X11R6/lib/libXmuu.so.1.0 >/usr/X11R6/lib/libXp.a /usr/X11R6/lib/libXpm.a /usr/X11R6/lib/libXpm.so >/usr/X11R6/lib/libXpm.so.4 /usr/X11R6/lib/libXpm.so.4.11 /usr/X11R6/lib/libXp.so >/usr/X11R6/lib/libXp.so.6 /usr/X11R6/lib/libXp.so.6.2 /usr/X11R6/lib/libXrandr.a >/usr/X11R6/lib/libXrandr.so /usr/X11R6/lib/libXrandr.so.1 >/usr/X11R6/lib/libXrandr.so.1.0 /usr/X11R6/lib/libXrender.a >/usr/X11R6/lib/libXrender.so /usr/X11R6/lib/libXrender.so.1 >/usr/X11R6/lib/libXrender.so.1.1 /usr/X11R6/lib/libxrx.so /usr/X11R6/lib/libxrx.so.6 >/usr/X11R6/lib/libxrx.so.6.3 /usr/X11R6/lib/libXss.a /usr/X11R6/lib/libXt.a >/usr/X11R6/lib/libXTrap.a /usr/X11R6/lib/libXTrap.so /usr/X11R6/lib/libXTrap.so.6 >/usr/X11R6/lib/libXTrap.so.6.4 /usr/X11R6/lib/libXt.so /usr/X11R6/lib/libXt.so.6 >/usr/X11R6/lib/libXt.so.6.0 /usr/X11R6/lib/libXtst.a /usr/X11R6/lib/libXtst.
