To get this thread back on topic, I've seen the first confirmation that Moorestown will use SGX graphics.
I've been doing some sniffing around for moorestown drivers, to confirm that it contains SGX. the open community is the best place to look, as its a collaborative environment.
If you look here:-
http://www.opensubscriber.com/message/dri-devel@lists.sourceforge.net/11716475.html
(warning its a BIG page),
You'll find "poulsbo/moorestown DRM driver"
There's a programming flag in there "IS_MRST" which is set when dealing with moorestown variation. In terms of graphics, the moorestown code is pretty much the same as the poulsbo (psb) code, with just some slight modifications and path variants. From that code I can confirm that Moorestown definitely has SGX in it, with the SGX registers in a different area of the memory map than in poulsbo, as this snippet of code reveals:-
if (IS_MRST(dev))
dev_priv->sgx_reg =
ioremap(resource_start + MRST_SGX_OFFSET,
PSB_SGX_SIZE);
else
dev_priv->sgx_reg =
ioremap(resource_start + PSB_SGX_OFFSET, PSB_SGX_SIZE);
later in the code, the offsets are defined as:-
PSB_SGX_OFFSET 0x40000
MRST_SGX_OFFSET 0x80000
The PCI_ID for moorestown is anything from 0x4100-0x4107, meaning they are allowing for the possibility of up to 8 sku variants. This could be simply different packages, clock rate, temp range etc.
#define psb_PCI_IDS \
{0x8086, 0x8108, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_PSB_8108}, \
{0x8086, 0x8109, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_PSB_8109}, \
{0x8086, 0x4100, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
{0x8086, 0x4101, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
{0x8086, 0x4102, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
{0x8086, 0x4103, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
{0x8086, 0x4104, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
{0x8086, 0x4105, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
{0x8086, 0x4106, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
{0x8086, 0x4107, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MRST_4100}, \
for comparision, the 8108 and 8109 ID's above for poulsbo are used to differentiate between the MID (L) and UMPC (W) versions of the existing SCH
Note that in general within the code, the moorestown variations seems to be dealt with in pretty much the same way as the poulsbo variation, with the clear suggestion thats its pretty much the same. There is nothing in the code that can be used to determine clock rates, so we dont' know if it operates at the same rate or quicker.
Some more interesting things are in the file.
First, Tungsten graphics are still involved. AS of Nov last year, they have been taken over by VMWARE and there is some VMWARE copyright headers in there.
Second, it appears from looking at the code, that the version of VXD that IMG supplied to Intel for poulsbo (and moorestown) is codenamed "topaz"
The above comments are my own personal interpretation of the code at that publicly accessible webpage. The file is dated March '09, so that must be borne in mind too
