Don't be confused into thinking that ATI's "CrossFire" dual video card configuration can be achieved with two "slave" cards as some might have you think.
DFI has been showing two slave cards running in a dual configuration at Computex as seen above, and they have in fact been showing 3DMark 2005 scores that increase by nearly 80% when they turn on "CrossFire" in the driver. Well to make a long story short, the two slave cards are sharing the workload and nearly doubling the 3D Mark2005 score, but you are only seeing every other frame supplied by one of the cards. So keep in mind that rendering double the frames is pretty "easy," but putting them back together again is not just going to happen by accident.
Anyway, chalk the confusion up to pre-release hardware and drivers. Kudos to DFI for finding something cool to share, but don't ever think you are going to reap the rewards of CrossFire rendering without a CrossFire hardware compositing engine to put all the frame or tiles back together again.
And just for the record, DOOM 3 showed absolutely no benefit from the configuration as you might guess.
Jawed said:Read the first posting I made in this thread.
Jawed
DaveBaumann said:I've come to the conclusion that the compositing engine is a performance optimisation. As I mentioned in our article, Super AA mode transfers the images via PCI Express, and some followup on that indicates that, right now (it is likely to change in the future, they just haven't had time yet) the composite engine is is more or less bypassed altogether for Super AA.
However, what this tells me is that the chips themselves are capable of the compositing (well, for Super AA they can certainly blend - I have seen two standard boards running before as well), but it would appear that to achieve this current boards need to get the input from the PCI Express bus (there is also the question of whether there is native hardware for this, or its actually running some kind of shader program), but this is not the optimal in terms of performance. The composite engine remove any reliance on the bus for the "performance" modes, also removes any necessity if the graphics core compositing has some overhead, and makes parallelisation a little easier.
We'll see how this changes once they have a seies of boards that were built with this in mind from the off.
Unknown Soldier said:Wouldn't they just be shooting themselves in the foot? I mean, most people think that Nvidia mobo's are tops .. but if those mobo's become incompatible with other graphics cards .. then they are gonna loose bigtime imo.
US
WaltC said:That aside, there is one aspect of nV SLI that I do indeed consider operates like a dongle, but it has nothing to do with the way the two nV cards are physically connected to each other. I am referring to the hardware on the dual-slot PCIe motherboards that has to be manually set by the user so that the motherboard will operate in dual-slot PCIe mode so that nV SLI is supported. Along with the fact that mobo makers are restricted from even advertising "SLI-capable" motherboards without paying nV a licensing fee, a dual-slot PCIe mboard ought to autoconfigure through its bios for dual-slot operation necessary to support *either* SLI or X-Fire, it seems to me. The fact that the PCIe bus specs as promulgated by Intel natively support dual-slot operation should have meant that a proprietary switching solution--especially one consisting of hardware on the motherboard external to the core logic--should be unnecessary. To this end it would seem the X-Fire switching, which apparently does not require control circuitry on the mboard external to the core logic, is much closer to the original Intel specification.
Walt, this is really ridiculous. First, you present a lengthy explanation how the word "dongle" has been misused, then you misuse it just a few lines on something that is nothing like the definition you told before. This routing card has absolutely nothing to do with authorization, it is a connector just like a cable is, and in those specific implementations is absolutely required for the pair of cards to work. Just like the Crossfire cable is required in this specific implementation, but could be replaced by something else.WaltC said:That aside, there is one aspect of nV SLI that I do indeed consider operates like a dongle, but it has nothing to do with the way the two nV cards are physically connected to each other. I am referring to the hardware on the dual-slot PCIe motherboards that has to be manually set by the user so that the motherboard will operate in dual-slot PCIe mode so that nV SLI is supported.
Do you think Crossfire certification comes for free?Along with the fact that mobo makers are restricted from even advertising "SLI-capable" motherboards without paying nV a licensing fee, a dual-slot PCIe mboard ought to autoconfigure through its bios for dual-slot operation necessary to support *either* SLI or X-Fire, it seems to me. The fact that the PCIe bus specs as promulgated by Intel natively support dual-slot operation should have meant that a proprietary switching solution--especially one consisting of hardware on the motherboard external to the core logic--should be unnecessary. To this end it would seem the X-Fire switching, which apparently does not require control circuitry on the mboard external to the core logic, is much closer to the original Intel specification.
geo said:http://www.theinquirer.net/?article=23593
Here's the actual article. Thinking back on Josh's interview with NV, maybe they're after making the pcie connection wide enough to do away with the intra-card connector without impacting performance? Folks might like that. Don't know what it would do to compatibility, if anything.
Xmas said:Walt, this is really ridiculous. First, you present a lengthy explanation how the word "dongle" has been misused, then you misuse it just a few lines on something that is nothing like the definition you told before. This routing card has absolutely nothing to do with authorization, it is a connector just like a cable is, and in those specific implementations is absolutely required for the pair of cards to work. Just like the Crossfire cable is required in this specific implementation, but could be replaced by something else.
Calling these connectors "dongles" is no more appropriate than, say, calling jumpers on a mainboard "dongles".
Xmas said:Oh, and I wish people would stop replacing "cross" or similar things with "X". That is just sooooo annoying...
That aside, there is one aspect of nV SLI that I do indeed consider operates like a dongle, but it has nothing to do with the way the two nV cards are physically connected to each other. I am referring to the hardware on the dual-slot PCIe motherboards that has to be manually set by the user so that the motherboard will operate in dual-slot PCIe mode so that nV SLI is supported. Along with the fact that mobo makers are restricted from even advertising "SLI-capable" motherboards without paying nV a licensing fee, a dual-slot PCIe mboard ought to autoconfigure through its bios for dual-slot operation necessary to support *either* SLI or X-Fire, it seems to me. The fact that the PCIe bus specs as promulgated by Intel natively support dual-slot operation should have meant that a proprietary switching solution--especially one consisting of hardware on the motherboard external to the core logic--should be unnecessary. To this end it would seem the X-Fire switching, which apparently does not require control circuitry on the mboard external to the core logic, is much closer to the original Intel specification.
WaltC said:The reason why I might loosely label that particular aspect as akin to a dongle is this: the core logic ought to be able to seamlessly configure a dual-slot PCIe-board without the need for manual "rerouters" or jumpers or any manual switches. The dual-slot PCIe config, remember, isn't custom or alien in any way to the PCIe spec advanced by Intel since the start. What nV's done, here, seems like deliberately configuring its nf chipset not to auto-switch transparently and to *require* some kind of artificial, chipset-extraneous mechanism to do the switching so that nV can call it proprietary and charge licensing fees for use of the circuitry. (Which makes sense considering that apparently nV has deliberately departed in this area from the Intel spec.) Again, of course, there's nothing dongle-ish about connecting the two cards to each other--it's what's happening at the chipset level on the mboard that I'm talking about.
IE, the manual switching mechanism is simply not needed in my view and is simply an artificially manufactured requirement for nF chipsets so as to make support for nV SLI proprietary and income producing.
NVIDIA = evil, and most of the time, he uses quite a lot words to say that.trinibwoy said:So exactly what is your point again?
WaltC said:The reason why I might loosely label that particular aspect as akin to a dongle is this: the core logic ought to be able to seamlessly configure a dual-slot PCIe-board without the need for manual "rerouters" or jumpers or any manual switches. The dual-slot PCIe config, remember, isn't custom or alien in any way to the PCIe spec advanced by Intel since the start.
What nV's done, here, seems like deliberately configuring its nf chipset not to auto-switch transparently and to *require* some kind of artificial, chipset-extraneous mechanism to do the switching so that nV can call it proprietary and charge licensing fees for use of the circuitry. (Which makes sense considering that apparently nV has deliberately departed in this area from the Intel spec.)
Again, of course, there's nothing dongle-ish about connecting the two cards to each other--it's what's happening at the chipset level on the mboard that I'm talking about.
IE, the manual switching mechanism is simply not needed in my view and is simply an artificially manufactured requirement for nF chipsets so as to make support for nV SLI proprietary and income producing.