[SOLVED] git

mark_alfred · 01-06-2010, 05:09 AM

I tried to follow the directions of this website, but wasn't able to get the right drm version. The site says to get version 2.4.1, and then gives instructions for getting drm. The instructions are: "Create a ~/src/drm-git directory and run git clone git://anongit.freedesktop.org/git/mesa/drm". I did this, but got drm version 2.4.17 rather than 2.4.1. Is there a way to search a git repository for different versions to download?

rnesius · 01-06-2010, 11:28 AM

I doubt getting drm 2.4.17 instead of 2.4.1 is going to cause you problems. The .17 should be rolling for bug-fix releases, not major compatibility changes. That said, I suggest finding your way to the mesa website where you /should/ be able to browse and download past releases.

CoderMan · 01-06-2010, 01:36 PM

Quote:

Originally Posted by mark_alfred

I tried to follow the directions of this website, but wasn't able to get the right drm version. The site says to get version 2.4.1, and then gives instructions for getting drm. The instructions are: "Create a ~/src/drm-git directory and run git clone git://anongit.freedesktop.org/git/mesa/drm". I did this, but got drm version 2.4.17 rather than 2.4.1. Is there a way to search a git repository for different versions to download?

I'm not familiar with that particular repository, but usually the devs have the different versions tagged. Go inside the repository directory and run the command "git tag". Usually you get a list of words, like so:

Code:

$ git tag
0.0.1
0.2.0
1.0.0
1.2.0
... and so forth ...

If you see the version you want, run "git checkout <tag>".

But, I actually think the other guy is right: 2.4.17 probably has the exact same API.

mark_alfred · 01-06-2010, 07:53 PM

Thanks for the responses. A problem I had after downloading the drm-2.4.17 thingy was that it didn't have what it was supposed to have (pardon my somewhat excessively non-technical description here, but in this realm, I'm proving to be a tad clueless). To be a bit more specific, the site mentioned this:

Quote:

Originally Posted by the How To Get 3D Graphics site said ...

Download drm revision 2.4.1 and extract it then

$ cd drm/linux-core

So, I tried going to the linux-core directory, but there was no such directory. Because of this, I wasn't able to complete building the mach64 module. I'll try checking out the other options that you gals/guys mentioned, such as the mesa site, or the git-tag. Anyway, if you've any further suggestions, please keep sharing.

mark_alfred · 01-06-2010, 10:00 PM

Okay, so I tried git tag, and got the following:

Code:

mark@debian:~$ git tag git://anongit.freedesktop.org/git/mesa/drm
fatal: Not a git repository
mark@debian:~$ git-tag git://anongit.freedesktop.org/git/mesa/drm
fatal: Not a git repository

I suspect I'm doing something wrong, but I have no clue as to what that is. If anyone knows of another repository where drm 2.4.1 resides, and especially if it's not a so-called git repository (which thus-far I'm finding incomprehensible), then by all means do tell.

[later edit]
Okay, I did figure it out. The tag thingy is for the repository I downloaded, which did work. The earliest it has is 2.4.15 (it has libdrm-2.4.1, though). I'll see if I can find another repository via the mesa website.

mark_alfred · 01-06-2010, 10:46 PM

Okay, good news! My noodle is slowly but surely starting to grasp how it can sometimes be useful to actually read other people's posts. In rereading coderman's post, I noticed that I had not fully taken his recommendations into account. So, this time I did, utilising the checkout advice, and got the following result:

Code:

mark@debian:~$ cd mach64
mark@debian:~/mach64$ cd drm
mark@debian:~/mach64/drm$ git checkout 2.4.15
Note: moving to "2.4.15" which isn't a local branch
If you want to create a new branch from this checkout, you may do so
(now or later) by using -b with the checkout command again. Example:
  git checkout -b <new_branch_name>
HEAD is now at a107e5b... Bump to 2.4.15 for release.
mark@debian:~/mach64/drm$ git checkout -b 2.4.15
Switched to a new branch "2.4.15"
mark@debian:~/mach64/drm$ cd linux-core
mark@debian:~/mach64/drm/linux-core$

So, I now have the linux-core directory. How exciting. I feel optimistic that I'll be playing planetpenguin-racer very soon now.

[later edit]
Well, I did get the mach64 module built, and got direct rendering going, but the results were a tad erratic; so, I've decided to forego my pursuit of planetpenguin-racer for now. However, I did figure out git to the extent that I could build the module; so, another successfully solved thread on LQ.

CoderMan · 01-07-2010, 12:45 AM

Quote:

Originally Posted by mark_alfred

Okay, good news! My noodle is slowly but surely starting to grasp how it can sometimes be useful to actually read other people's posts. In rereading coderman's post, I noticed that I had not fully taken his recommendations into account. So, this time I did, utilising the checkout advice, and got the following result:

Code:

mark@debian:~$ cd mach64
mark@debian:~/mach64$ cd drm
mark@debian:~/mach64/drm$ git checkout 2.4.15
Note: moving to "2.4.15" which isn't a local branch
If you want to create a new branch from this checkout, you may do so
(now or later) by using -b with the checkout command again. Example:
  git checkout -b <new_branch_name>
HEAD is now at a107e5b... Bump to 2.4.15 for release.
mark@debian:~/mach64/drm$ git checkout -b 2.4.15
Switched to a new branch "2.4.15"
mark@debian:~/mach64/drm$ cd linux-core
mark@debian:~/mach64/drm/linux-core$

So, I now have the linux-core directory. How exciting. I feel optimistic that I'll be playing planetpenguin-racer very soon now.

[later edit]
Well, I did get the mach64 module built, and got direct rendering going, but the results were a tad erratic; so, I've decided to forego my pursuit of planetpenguin-racer for now. However, I did figure out git to the extent that I could build the module; so, another successfully solved thread on LQ.

If I may: Your profile says that your distribution is Debian. Planet-Penguin Racer 0.3.1 is in Debian Lenny (stable) and Planet Penguin Racer 0.5beta is in Debian Squeeze (experimental). Have you tried:

Code:

$ apt-get install planetpenguin-racer

mark_alfred · 01-07-2010, 11:27 AM

Yes, I have. planetpenguin-racer was merely a light way to reference that my machine does not have 3d acceleration (aka direct rendering) of any sort going on; so, while ppr works, it works very slowly -- so slow that it cannot be played. So, getting direct rendering going would allow me to more successfully play ppr.

photor · 05-28-2010, 07:35 AM

Quote:

Originally Posted by mark_alfred

Okay, good news! My noodle is slowly but surely starting to grasp how it can sometimes be useful to actually read other people's posts. In rereading coderman's post, I noticed that I had not fully taken his recommendations into account. So, this time I did, utilising the checkout advice, and got the following result:

Code:

mark@debian:~$ cd mach64
mark@debian:~/mach64$ cd drm
mark@debian:~/mach64/drm$ git checkout 2.4.15
Note: moving to "2.4.15" which isn't a local branch
If you want to create a new branch from this checkout, you may do so
(now or later) by using -b with the checkout command again. Example:
  git checkout -b <new_branch_name>
HEAD is now at a107e5b... Bump to 2.4.15 for release.
mark@debian:~/mach64/drm$ git checkout -b 2.4.15
Switched to a new branch "2.4.15"
mark@debian:~/mach64/drm$ cd linux-core
mark@debian:~/mach64/drm/linux-core$

So, I now have the linux-core directory. How exciting. I feel optimistic that I'll be playing planetpenguin-racer very soon now.

[later edit]
Well, I did get the mach64 module built, and got direct rendering going, but the results were a tad erratic; so, I've decided to forego my pursuit of planetpenguin-racer for now. However, I did figure out git to the extent that I could build the module; so, another successfully solved thread on LQ.

I have tried your method and entered the linux-core directory, but when I tried to compile with "make mach64.o", I got the following error:
...
~/drm/linux-core/drm_memory.c: In function ‘agp_remap’:
~/drm/linux-core/drm_memory.c:286: error: ‘struct agp_memory’ has no member named ‘memory’
...
Please help me!

craigevil · 05-28-2010, 10:07 AM

git is one of those evil things that either works right or it drives you crazy. The README says it all

/usr/share/doc/git

Quote:

"git" can mean anything, depending on your mood.

- random three-letter combination that is pronounceable, and not
actually used by any common UNIX command. The fact that it is a
mispronunciation of "get" may or may not be relevant.
- stupid. contemptible and despicable. simple. Take your pick from the
dictionary of slang.
- "global information tracker": you're in a good mood, and it actually
works for you. Angels sing, and a light suddenly fills the room.
- "goddamn idiotic truckload of sh*t": when it breaks

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

Or you can be lazy and use one of the numerous GUIs for git. git-cola is nice and has a nice guide.
file:///usr/share/doc/git-cola/html/userguide.html