"Ask ATI" dev thread

[cutterjohn]

Qaridarium , don't get excited to soon. Evergreen is made by TSMC.

And their 40nm process is extremely leaky. So to see good power numbers would mean that TSMC solved a problem haunting them for the last 12 month.

*snicker* right, the root cause of the nVidia GPU problem(Pb free solder kindof) fixes their half---ed 40nm process... right.

Switching between IGP & discrete has never seemed to work well unless it involved a way to physically shut downt he discrete GPU which AFAIK was only ever really done on the ASUS netbook with an Intel IGP & nVidia disrete 9300M via a physical/soft switch.

I've read about other designs attempting to meld same copany IGP & discrete GPUs together to improve performance, but can't recall any notebok that actualy implemented this.

(Oh God, my eyes are bleeding worse than reading World of Gothic English forums...)

[energyman]

I am not saying that nvidia's problems are caused by TSMCs leaky 40nm.

I never did that. But hey, you are free to not-read whatever you want,

Fact is, all cards produced in 40nm use a lot more power than most people expected. TSMC's process is known leaky - and even TSMC admitted that. Leaky means hot. Leaky is BAD.

This problem is well known.

And has nothing to do with Nvidia's bumpgate CF.

[V!NCENT]

Hey I have a question:
Does ATI have any plans for future cards to make them more documentation and FLOSS friendly? Or is this confidential?

I am asking this because releasing documentation was said to be kind of a tricky thing to do and had to be done very carefully.

[bridgman]

I don't expect things to get a lot easier from an IP perspective.

The main improvement will be that now we are "caught up" with new GPU introduction and able to work on open source docs and support while our hardware and software engineers still have a good chance of remembering what they had to do in order to make the chip work

[V!NCENT]

I don't expect things to get a lot easier from an IP perspective.

The main improvement will be that now we are "caught up" with new GPU introduction and able to work on open source docs and support while our hardware and software engineers still have a good chance of remembering what they had to do in order to make the chip work

Thanks for the info So there are no seperate DRM circuits and such?

[bridgman]

So far the added per-chip cost and power impact of implementing separate DRM and non-DRM programming models has been too high. It's not a question of just separating blocks, unfortunately.

[V!NCENT]

So far the added per-chip cost and power impact of implementing separate DRM and non-DRM programming models has been too high. It's not a question of just separating blocks, unfortunately.

Yeah I was already afraid of such a thing =x

[daniel.blueman]

One key question to the ATI/AMD devs:

How can we engage the Linux community to work better with ATI/AMD to help track and report problems at http://ati.cchtml.com?

There are many stale bug reports, and poor education about reporting bugs here, rather at the distro level. The ATI/AMD world is disconnected from the user-world by this, and we need to find a way to connect the two.

Perhaps it's a good start that ATI/AMD does some tidying up in this bug tracking system?

[Qaridarium]

Yeah I was already afraid of such a thing =x

bridgman can not talk on unreleased produkts!

bridgman only talk abaut hd4000 and hd5000

bridgman is unter NDA abaut the R900 hd6000 series!

and no... NDA of bridgman means he can not answer any question abaut this.

there is a chance for the R900 to have a fullfeatures opensource viedeo acceleration.

[Qaridarium]

One key question to the ATI/AMD devs:

How can we engage the Linux community to work better with ATI/AMD to help track and report problems at http://ati.cchtml.com?

There are many stale bug reports, and poor education about reporting bugs here, rather at the distro level. The ATI/AMD world is disconnected from the user-world by this, and we need to find a way to connect the two.

Perhaps it's a good start that ATI/AMD does some tidying up in this bug tracking system?

thats an illusion! because nearly all important people are in the beta-driver program and sign NDA paper.

for an exampel: kano write a lot in this forum and he speak clear words..

but why??? he is not in the beta programm no NDA!...


for the cloused source FGLRX driver its pointless to report bugs in the stable driver! becouse the betas are 2-3 versions in the future!

you do not know if your bug allready fixed in the future drivers becouse you do not have access to the beta drivers!

if you realy wana help the FGLRX ... sign a NDA and report bugs in the Beta programm..

the DEV's read this directly and fix the problem directly!


"http://ati.cchtml.com" is a bad Joke becouse of the cloused beta programm.