tag:blogger.com,1999:blog-36137506.post4076783549746249555..comments2024-02-09T15:22:59.181+01:00Comments on Tagebuch eines Interplanetaren Botschafters: Radeon 3D Wiki driveNicolai Hähnlehttp://www.blogger.com/profile/18235566517992076346noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-36137506.post-65113906881270976092009-11-09T23:33:05.820+01:002009-11-09T23:33:05.820+01:00One thing that would help me, is describing a typi...One thing that would help me, is describing a typical SW setup to do driver debugging and development.<br />Ive got enough experience in userland 3d dev, some embedded and windows driver dev etc, just that i havent seen a short "getting started" guide or "setting up environment" guide for doing mesa driver dev without locking up Xorg on my main machine all the time.telexhttps://www.blogger.com/profile/13546884838263786497noreply@blogger.comtag:blogger.com,1999:blog-36137506.post-17562257790938831952009-10-14T12:36:37.762+02:002009-10-14T12:36:37.762+02:00Rafal: Thanks to open source, the functionality of...Rafal: Thanks to open source, the functionality of glxgears doesn't have to remain a mystery. The source to glxgears is in Mesa, in the file <a href="http://cgit.freedesktop.org/mesa/mesa/tree/progs/xdemos/glxgears.c" rel="nofollow">progs/xdemos/glxgears.c</a>.<br /><br />The original version, gears, uses the <a href="http://en.wikipedia.org/wiki/OpenGL_Utility_Toolkit" rel="nofollow">GLUT</a> library, which means that it doesn't contain any X window calls but only OpenGL calls, which should make the OpenGL aspects of the program easier to understand. You can find the source in <a href="http://cgit.freedesktop.org/mesa/mesa/tree/progs/demos/gears.c" rel="nofollow">gears.c</a>.<br /><br />skierpage: The thing is, all this information is already on the X.org and DRI wikis. Maybe it needs to be made more accessible. Perhaps a "how to learn to understand what the heck is going on" kind of introduction would be helpful.<br /><br />egore911: Yes I know, and I'm grateful for what you did and still do. As for attracting new developers, I have the feeling that driver development is just fundamentally hard and we just cannot expect to get hordes of new developers, but still I feel that by trying to lower the bars just a little bit, we can increase the chances of attracting new developers. Unfortunately, we'll probably never be able to say "this guy/gal started hacking the driver because of this Wiki page" unless they personally tell us that. Because of that, it may seem futile at times, but I'm pretty sure it's not.<br /><br />In the long run, we just need to find a mode of operation where we occasionally do small things to the Wiki to keep it up to date without spending too much time on it.Nicolai Hähnlehttps://www.blogger.com/profile/18235566517992076346noreply@blogger.comtag:blogger.com,1999:blog-36137506.post-69398396567466327752009-10-14T09:13:09.392+02:002009-10-14T09:13:09.392+02:00I tried to do the "marketing" stuff usin...I tried to do the "marketing" stuff using tirdc. I don't think it really gathered developers, but it was good to do something in the public. I currently totally lack the time, so I only randomly publish information. Hope we can improve this situation together. Thanks for your hard efforts!Anonymoushttps://www.blogger.com/profile/15531393382879891421noreply@blogger.comtag:blogger.com,1999:blog-36137506.post-73225140514315325132009-10-14T08:35:39.843+02:002009-10-14T08:35:39.843+02:00I sort of understand how my ATI 9800 All-in-Wonder...I sort of understand how my ATI 9800 All-in-Wonder pro card relates to X (X loads radeon_drv.so because that is the open-source video driver supporting the R350 chip ). Until your post I had no idea if there is a separate DRI driver, or how to tell what the mysterious "mesa" uses.<br /><br />glxinfo reports "OpenGL vendor string: DRI R300 Project" but there's no indication of it loading any driver. So when your Radeon portal page starts talking about the "r300" driver, I was completely mystified. Now looking much further down in Xorg.0.log I see "(II) AIGLX: Loaded and initialized /usr/lib/dri/r300_dri.so". Live and learn! (One problem with the DRI project is searching for "dri" returns so many matches for "driver".)<br /><br />I think you need to step back and explain the basics on the DRI wiki: "Your card has a video driver for the X Window System, and may also have a separate DRI driver for 3D acceleration. You can find out what driver is used for each by... looking in /var/log/Xorg.0.log(?) You can tell what 3D in X uses by ... running glxinfo (?)"<br /><br />Cheers.skierpagehttps://www.blogger.com/profile/04480517078252023572noreply@blogger.comtag:blogger.com,1999:blog-36137506.post-52273122016033184682009-10-13T23:38:00.237+02:002009-10-13T23:38:00.237+02:00Huh, thanks for looking at this :)
I'll try t...Huh, thanks for looking at this :)<br /><br />I'll try to hack on something, but it will definitely take me some time to just read the docs.<br /><br />Could you tell me if my understanding of general 3D rendering is correct? Here is how I imagine glxgears:<br /><br />[first,once: init gpu]<br />driver tells GPU to create new contex<br />driver sends GPU eye coords<br />for (i = 0..2) {<br /> driver tells GPU to use colors[i]<br /> driver draws gear<br />}<br />while (1) {<br /> for (0..2) {<br /> rotate += 1<br /> }<br />}<br /><br />OK, that probably looks silly for you... ;) But maybe there are some important steps I missed, or I get sth totally wrong. Or maybe my knowledge should be more detailed? So I could understand code flow better?Unknownhttps://www.blogger.com/profile/10470581669178400437noreply@blogger.com