Log in

No account? Create an account

July 2017
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31

airlied [userpic]
r500 3D docs released + come on all you "hackers"

So AMD released r500 3D programming information today, the most interesting piece being the r500 fragment shader programming guide which allows us to maybe get r300 into some kind of shape for r500 use.

So along with the intel 965 docs, we now have 2 fairly well documented chips. So an excuse I've always heard from people turning up on irc channels is OMG I can't hack on GPU drivers there are no docs!!!. So now that we have these docs I'm expecting a large amount of developers to be able to bootstrap themselves on modern hardware. I wonder how disappointed I'm going to be.

updated: http://www.x.org/docs/AMD/ is the docs location, the newest pdf is the r500 3D engine manual.


Dude, you shouldn't set yourself up for such disappointments. It's like lining up repeatedly for electroshock therapy


Does this mean that we will also see better performance for R300 and real RENDER acceleration?

It'd be great to be able to use xcompmgr at full speed. I can't stand the compiz crap...

What are the prerequisites for R300/R420 hacking?
(Other than having the hardware handy, and knowing C.)

(no subject) - (Anonymous)

Awsome. Thanks for the info!

I think that the barrier to entry to X hacking is still quite high. Of course some of this is unavoidable due to the number of interlinked dependencies. If I want to indulge in a little kernel hacking it's quite easy to throw a new kernel on your machine without building a new user space. X hacking seems to involved getting kernel, X from src and DRI and mesa all built just to try stuff out.

I was under the impression that the new modular X would make it easier to just build a component and test within a working X setup. If it's not the case and it's best to do a full src install it would probably be useful to have a page describing how one runs a parallel X install without hosing the distro version of X. Most casual developers are only likely to have one machine and it can keep quite daunting if your run the risk of killing a working setup.

The link to the development documentation is useful but despite the text indicating there are instructions on how to get started it's not immediately clear what pages are worth reading first. What would be useful is a "GettingStartedWithXDevelopment" page linked at the top of the Developer page with notes of how a potential developer should set-up their development environment so they can make their first steps into the world of X hacking.

(no subject) - (Anonymous)

That's a useful write-up. I shall have to see how easily that builds on my Gentoo system (dev packages are kinda the default). But I'll certainly have a play.

Provided that the rest of your stack is new enough, you should be able to just install all the -devel versions and then hack on your one component. If you just wanted to hack on the X video driver (not the 3D driver) then you could definitely just pull that driver's source and play with your system as is.

Getting the 3D side involved probably means something a little more like ajax is suggesting. However, if your system mesa is new enough, you might be able to get away with just replacing the single DRI driver and leaving the rest alone.

Even Kristian's instructions where he's hacking on DRI (which intertwines into every part of the graphics stack), he still doesn't have to rebuild all of X. He's using his system's X libraries, headers and applications.

You should not buy one if you aren't going to be able to act as your own technical support. " --Hyde and Geek (blogspot) Moral of the story.

3D Flightsim

As editor of AV CONCEPTS (now with 7000 weekly readers) I am always on the lookout for news and information of 3D as per this one; please feel free to contact me.
Tony Shapps
Now with over 7000 readers weekly.
Subscribe to 'AV CONCEPTS' by sending a BLANK
or visit me at:

one has to admit that X hacking is very elite.... (I'm talking about technical level of entry).

So where *are* these docs?

Linky? Nothing on developer.amd.com that I can see, or lwn.net or freedesktop.org...

Re: So where *are* these docs?

Ya. I'd like to see this also...

Oh, and this is terrific news.

Re: So where *are* these docs?

Thank you!

Re: So where *are* these docs?

Just feel with you