0 Members and 1 Guest are viewing this topic.
When i saw those results posted earlier i got curious how memory speed would be without saga running at all...Some explanations on results you see here.v500+ pal2: saga monitor driver is not in devs/monitors, and running pal640x256x4 when testing.v500+ pal1: saga monitor driver is loaded from devs/monitors, but the resolution is switched to pal640x256x4 before running the test.you: this is test is run with the screen resolution you see in the screenmode prefs window on the screen. This is the same saga resoultion used in v500+pal1 test, so switching to no-saga resolutions seems to have the saga-core running in the background when not used.running v500+ gold core 2, and i believe x11 speed.cheers!
To get full speed when using the chipset, you need to use a special command to deactivate the HDMI output. The trouble is, I don't remember the custom command. It is one that was created by the team.
http://wiki.apollo-accelerators.com/doku.php/sagasleep
yes, i think this is the reason. might be considered a hardware flaw and maybe to be corrected in future implementations. likely there is pros and contras using unified versus separate ram for main memory and rtg.
So how about speeding up the video clock , putting 1GB of memory on the card and let Saga have whatever it needs?
I read that the new board design was to allow higher clock. We'll see if it works.
The newer board design is likely to use a newer FPGA. For example, a Cyclone 5 supports DDR3 memory while current designs use a Cyclone 3 with SDRAM.
Which Vampire board design are you referring to? Vampire 500 V2 to Vampire 500 V2+? Other?