Re: [Dri-devel] [volodya@mindspring.com: [Xpert]Guide to debuggingDRI installations]

2001-06-22 Thread Jens Owen
[EMAIL PROTECTED] wrote: > > On Thu, 21 Jun 2001, Jens Owen wrote: > > > Vladimir, > > > > Your page looks very helpful. Thanks for putting it together. The only > > comment I have is regarding your first miscellaneous comment: > > > > "While hardware 3d is active nothing except your Xserver s

Re: [Dri-devel] [volodya@mindspring.com: [Xpert]Guide to debugging DRI installations]

2001-06-22 Thread Jens Owen
Vladimir, Your page looks very helpful. Thanks for putting it together. The only comment I have is regarding your first miscellaneous comment: "While hardware 3d is active nothing except your Xserver should be accessing your video card - or your system will lockup hard. In particular, frame gr

Re: [Dri-devel] Mesa 3.5 heads-up

2001-06-22 Thread Jens Owen
Brian Paul wrote: > > I'm planning on releasing Mesa 3.5 (the stand-alone version) tomorrow. To: Brian, Keith, and everyone else who has contributed to the 3.5 branch. This is great news! This redesign is a big step forward and to be starting the integration of this code into the main developm

Re: [Dri-devel] Re: [Xpert]Guide to debugging DRI installations

2001-06-22 Thread volodya
On Thu, 21 Jun 2001, Frank Worsley wrote: > > I put the page together after trying to walk thru several > > people with buggy Redhat installs. For some reason things like ldd or > > strace are not as well known to new users as they should be. > > The problem here is not so much that people don

Re: [Dri-devel] r128 version bump

2001-06-22 Thread Michel Dänzer
Brian Paul wrote: > > Michel Dänzer wrote: > > > > Brian Paul wrote: > > > > > No need to bump version number as this value isn't used anywhere in > > > the kernel module. > > > > Speaking of a version bump, it looks like the _major_ of the r128 driver > > in the trunk needs to be bumped (see

Re: [Dri-devel] r128 version bump

2001-06-22 Thread Brian Paul
Michel Dänzer wrote: > > Brian Paul wrote: > > > No need to bump version number as this value isn't used anywhere in > > the kernel module. > > Speaking of a version bump, it looks like the _major_ of the r128 driver in > the trunk needs to be bumped (see discussion on the Xpert list). I'm