drkohler said:
Technically that is incorrect, as the eSRam "has no address" so it can't be unified per se. The situation is too complex to go into details, but basically the user has to manage the four 8MByte esram blocks at all times, except if you sort-of "abused" the esram as a simple buffer of some type, like frame buffers (bad idea) or back-end buffers (good idea). The phrase "“We haven’t played around with the eSRAM much yet." immediately makes it clear their software is currently struggling with 30Hz, but that is likely the problem for the grunt people to solve, not the tech director, whose job is to say nice things about her/his software. |
Interesting, so the eSRAM is neither dedicated nor unified. Is that the same situation with the X360's EDRAM?
“The fundamental cause of the trouble is that in the modern world the stupid are cocksure while the intelligent are full of doubt.” - Bertrand Russell
"When the power of love overcomes the love of power, the world will know peace."
Jimi Hendrix
