<br><br><div class="gmail_quote">On Sun, Jul 11, 2010 at 4:21 PM, Roderick Colenbrander <span dir="ltr"><<a href="mailto:thunderbird2k@gmail.com">thunderbird2k@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5"><br>
</div></div>The PCI id is something else. For instance run 'lspci -x':<br>
01:00.1 Audio device: ATI Technologies Inc RV620 Audio device [Radeon<br>
HD 34xx Series]<br>
00: 02 10 28 aa 07 01 10 40 00 00 03 04 10 00 80 00<br>
..<br>
<br>
This line shows a part of the PCI configuration header. The first two<br>
bytes contain the PCI vendor id (0x1002 = ATI; you have to swap the<br>
bytes) and byte 3 and 4 contain the PCI device id (0xaa28 = radeon<br>
3450). Each device has such information and it is used by the<br>
operating system to detect which hardware is around.<br>
<br>
A lot of games use the PCI id, since it can be easier to parse than<br>
the renderer strings.<br>
<div class="im"><br></div></blockquote><div><br>That makes sense. I had based my thinking on the following comment,<br><br>A Direct3D device object contains the PCI id (vendor + device) of the videocard which is used for rendering.<br>
<br>I had assumed vendor + device meant the strings.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
<br>
</div>We have to keep the current static database. Extending it with video<br>
memory reporting is likely the best way to go. So now and then it just<br>
means that we have to refine it a little.<br>
<font color="#888888"><br>
Roderick<br>
</font></blockquote></div><br>Thinking things over I think you are right. Trying to add any kind of dynamic support at this stage is not worth it. Even the memory reporting is very recent and new. Maybe in a couple years more support will have materialized from opengl or the drivers to help with this issue. For now though I just submitted a patch to deal with the issue of a 8500/8400 being reported as a 8300. I moved the detection to be reported as an 8600. I thought about creating a new 8500 in the database but I realized that an 8600 is of feature parity and has the same video memory minimum.<br>
<br><br>Thanks,<br><br>Seth Shelnutt<br>