[Mesa-dev] mesa: remove-driver-date GIT branch

Sedat Dilek sedat.dilek at googlemail.com
Tue Apr 5 03:04:15 PDT 2011


On Mon, Apr 4, 2011 at 6:34 PM, Ian Romanick <idr at freedesktop.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 04/03/2011 02:15 PM, Sedat Dilek wrote:
>> WOW!
>> Just remembered my approach (witch patches and rants) to remove
>> core-date and driver-date from kernel (drm-2.6) and libdrm as the
>> version are simply unmaintained.
>> Looks like I am not alone :-).
>
> There is also an e-mail thread[1] about these patches.  Review comments
> are welcome.
>
> [1] http://lists.freedesktop.org/archives/mesa-dev/2011-March/006321.html

Hi Ian,

first of all I am really glad that mesa gets rid of this unmaintained
driver-date stuff.
It is fooling users and helps to relax maintainers.
I offered a patchset for kernel-drm and libdrm in January to remove
DRM driver-date and core-date.
Maybe, I do a take #2 after your work is accepted in mesa master GIT.

I have tested your remove-driver-date GIT branch in mesa with a
linux-next kernel (next-20110405 plus drm-fixes) on a Debian/sid i386
host with a radeon RV250 (see glxinfo output below).
Libdrm is Debian's 2.4.24 and xserver Debian's 1.10.1-RC1 from
experimental branch.

$ cat /proc/version
Linux version 2.6.39-rc1-next20110405.3-686-small (Debian
2.6.39~rc1-3~next20110405.dileks3) (sedat.dilek at gmail.com) (gcc
version 4.6.1 20110329 (prerelease) (Debian 4.6.0-2) ) #1 SMP Tue Apr
5 10:52:55 CEST 2011

$ git log --pretty=short -1
commit 00b28b10f4435e64a5fe37acae8c3da773e5bb8a
Author: Ian Romanick <ian.d.romanick at intel.com>

    mesa: Include GIT SHA1 in GL version string

glxinfo now says:

$ glxinfo | grep -i opengl
Mesa warning: couldn't open libtxc_dxtn.so, software DXTn
compression/decompression unavailable
OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI R200 (RV250 4C66) x86/MMX/SSE2 TCL DRI2
OpenGL version string: 1.3 Mesa 7.11-devel (00b28b1)
OpenGL extensions:

For the version string:
What about "git-$GITHASH" in parantheses? A sole number might say
nothing to users?
Be user-friendly as possible.

Feel free to add a:

     Tested-by: Sedat Dilek <sedat.dilek at gmail.com>

- Sedat -


More information about the mesa-dev mailing list