-3
\$\begingroup\$

I searched on the web if there is any documentation about designing a video card using existing GPU (NVDIA/AMD). Let's say, ASUS, MSI and other brands design GTX 960 cards using the same GPU. I'd like to know if there is any good documentation for interfacing a GPU and the multiple modules on board (memory, power supply, bus, etc.) as I seem to not be able to find one.

I only found this link but seems a bit on the software side? https://media.readthedocs.org/pdf/envytools/latest/envytools.pdf

It seems I can't find any gpu pinout like standard processors/fpgas have?

\$\endgroup\$
5
  • 3
    \$\begingroup\$ This type of design documentation could well be buried in NDAs and may not be freely available online. \$\endgroup\$ Commented Sep 27, 2016 at 2:23
  • 2
    \$\begingroup\$ Probably because that info is not publicly released and you're not ASUS, MSI or similar. \$\endgroup\$
    – brhans
    Commented Sep 27, 2016 at 2:24
  • \$\begingroup\$ Agreed. I bet you would have to sign an NDA to see the detailed specs on any modern GPU. Also, this is not a job for the faint-of-heart. :) \$\endgroup\$ Commented Sep 27, 2016 at 3:20
  • 5
    \$\begingroup\$ Sorry if this comes off as harsh, but consider the difficulty a useful reality check: This is the type of question, which in the very asking demonstrates that the project is not within the present reach or resources of the person who would ask it here. It's basically a given that someone who has built something a usefully preparing fraction as complicated is already going to know why this information is not readily available, and the path that would have to be followed by a company seeking access to it. \$\endgroup\$ Commented Sep 27, 2016 at 4:50
  • \$\begingroup\$ @lucas92 I'm sure if your prepared to buy GPU's in quantities of thousands any one of these companies would be happy to talk to you and give you any relevant information \$\endgroup\$
    – Voltage Spike
    Commented Sep 27, 2016 at 15:58

1 Answer 1

2
\$\begingroup\$

To design with the more complex parts and the most advanced technologies you really have to climb into bed with the manufacturer. The main reason for this is that designing with parts like this takes a lot of support from the manufacturer which translates into a high cost for them. They want to make sure that you are fully committed to designing with their parts and want to understand fully what your end marketplace potential really is. This in turn allows them to calibrate the value that you represent to them as a customer.

To protect the "break-in" interface with them they often hold detailed specifications close to their chest and only reveal them to committed customers. Often time the first step is contacting their sales organization and/or field applications engineers. You will be asked to sign an NDA (Non Disclosure Agreement) before they will give you access to documentation. This keeps such documentation from getting out into the wild where non-vetted customers would have access to it. In some cases this also gives access to pricing data as fits your customer application and usage volume profile.

To mitigate initial technology evaluation manufacturers will often produce reference boards that you can purchase to "play" with the technology before any NDAs may be necessary. After the documentation is made available it is not uncommon that it will become obvious that the manufacturer will indicate that for the best success that you design your product very closely following the reference design to which they will provide schematics and even full PC board design files. In some cases a very detailed step by step design guide may be provided.

With all of the above said there are still manufacturers that do not privatize the availability of detailed product documentation. (Most FPGA vendors are a good example of this). The trade off for this is that the price for the most high tech parts may be in the 100's of dollars (if not 1000s).

\$\endgroup\$

Not the answer you're looking for? Browse other questions tagged or ask your own question.