Linked by Thom Holwerda on Tue 15th Jan 2008 17:00 UTC, submitted by anonymous
Thread beginning with comment 296339
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Programmable hardware
by Earl Colby pottinger on Thu 17th Jan 2008 03:59
in reply to "RE[2]: Programmable hardware"
Because then you are not directly working with a single frame buffer, you either end up shadowing the frame buffer in main memory and have to copy that to the separate buffers in the video cards, or your software has to figure out which card it is drawing to on the fly.
Either method has a lot of overhead.
RE[4]: Programmable hardware
by WereCatf on Thu 17th Jan 2008 04:58
in reply to "RE[3]: Programmable hardware"
Well, if your software really has to have direct access to the hardware frame buffer.. But if your app was just an X application X would present all the screens to it as just one large screen and you could render anything you wish and leave the rest to X. Though, I don't have a clue what you're planning so can't really help more than that 
RE[3]: Programmable hardware
by Earl Colby pottinger on Thu 17th Jan 2008 04:00
in reply to "RE[2]: Programmable hardware"





Member since:
2006-02-15
Why not just use two separate cards with dual output each? Atleast X can use all the screens as a large single one. Or is it a Windows based project you'd need that for?