On Wed, 3 Oct 2001, David Johnson wrote:
>
>
>
> >From: [EMAIL PROTECTED]
> >Reply-To: [EMAIL PROTECTED]
> >To: [EMAIL PROTECTED]
> >Subject: Re: [Dri-devel] Radeon 8500, what's the plan?
> >Date: Tue, 2 Oct 2001 17:19:53 -0400 (EDT)
> >
> >
> >
> >Well, we (GATOS) do have the docs, under similar NDA. I believe PI/VA was
> >more "doc-rich" ;) But (looking in them) they document at least basic 3d
> >functionality (don't know about TL and stuff, have not looked thoroughly
> >enough). Keep in mind that what we get is much better than nothing but not
> >as good as we would like. Probably, when ATI writes drivers internally
> >they rely on talking to their hardware people too much.
>
> I think you probably got the same docs that PI/VA got and those docs are
> fairly complete. The advantage of ATI engineers is that they can talk
> directly to the people who designed the chip.
>
> >PSS Doc-rich refers to them allegedly having documentation for iDCT. Now,
> >for conspiracy people, consider this: Loki had iDCT docs and they are in
> >trouble, PI/VA got them - and VA is downsizing.. ;) Just kidding..
>
> Loki didn't get low level (i.e. register level) idct docs. They got an idct
> library with docs on how to use that library. I don't think PI/VA got them
> either. There is some seriously proprietary stuff with idct that for legal
> reasons ATI wouldn't want to expose.
Would you know which legal reasons ? I.e. is that only ATI will get into
trouble if the publish the docs, or anyone that figures out how iDCT works
is liable ?
thanks
Vladimir Dergachev
>
> David
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
