That's like Xmas for me

While it is unfortunate that all chips prior to the R500 may not have documentation released.. don't those cards already have working drivers for accelerated 2D/3D operations?Combuster wrote:Now to wait for them to release docs on the older chips so I can put my grand collection of old Rage chips to work (or my R400, pretty please)
Trying to send a message to [email protected]: "Dude, read some of my older posts. Don't you think I have tried? I did." Connection LostBrynet-Inc wrote:As for the Rage cards, Just look at the Mach64 Mesa/DRM/DRI driver Combuster, I know it's not your most favourite programming language.. but I'm sure you'll be able to construct a basic understanding of the cards in question.
Let's hope it's true.. and the specifications are available for anyone who wants them.An OSNews Article wrote:This morning at the X Developer Summit in the United Kingdom, Matthew Tippett and John Bridgman of AMD have announced that they will be releasing their ATI GPU specifications without any Non-Disclosure Agreements needed by the developers! In other words, their GPU specifications will be given to developers in the open.
Therefore you shouldn't need to worry about another R200 incident taking place. The 2D specifications will be released very soon and the 3D ones will follow shortly.
Maybe not. But unlike the software industry, what has the hardware industry to loose by releasing driver source code? We still have to buy their hardware to use their code! And it'll increase sales because the tiny percentage of people will know the hardware is supported in their favourite OS.Solar wrote:Unlikely. nVidia has finally won the race for the high-end 3D marketplace. Why should they undisclose anything?SpooK wrote:Hopefully that forces nVidia's hand.
The argument always was, the driver sources would allow the competition to figure out large parts of how the chips worked internally.MessiahAndrw wrote:But unlike the software industry, what has the hardware industry to loose by releasing driver source code?
That is what's happening.I could have this all wrong and possibly it had the driver as a pre-compiled object and only compiled the kernel glue code to link to to create the driver module.
I wouldn't necessarily be that optimistic either. A modern video card driver includes a compiler to convert some sort of generic "shader language" into GPU specific code, which is one of the reasons a decent video driver can be larger than a decent (monolithic) kernel like Linux. Even if AMD provide extremely good documentation for everything (including the GPU and all the additional stuff), it might still take several years for an experienced video driver programmer to create a "full function" video driver.SpooK wrote:At any rate, such information will be devoured by OSDev.org and we'll have neater looking hobby OSes in no time... just get ready for more non-RTFM-compliant types